Virtual pins ARE a Blynk invention and primary process… NOT a workaround
As for what Blynk is about… don’t make such hasty assumptions. Blynk is an IoT application that provides a GUI and ease of communication between you and your IoT hardware. Yes, that can be done to a limited level without much coding, but that is really only for getting your feet wet, so to speak, or for less complicated projects.
If you really want to see your Blynk projects shine, you will need to learn how to use all those “coding” commands and Virtual pins that Blynk took all that time to create and document. Now, why do YOU think they did all that if it is “just” a workaround?
The developers always read these posts… so, if they feel that you have found an issue, then they will get involved.
As for your issues… I don’t find you post very clear as to the precise nature of said issue.
ESP devices have known situations where various pins boot HIGH.
Or perhaps some of your App’s button states are being activated upon App start for a logical reason, etc…
If you have truly read through all the documentation, and much of the forum, and have updated to all the current versions of Library and App, and still see a reproducible “issue” then please clearly document and provide App settings of such, so others can try to duplicate it.