I changed your topic to a Need Help category… since I highly doubt Blynk is going to just drop what they have already built and redesign it in whatever unique way you thing it should be 
I am not a developer… but they are busy and might not respond right away, so I will try to assist with some clarifications as best as I am able.
Not sure how you could have come up with that impression… have you done any previous Arduino coding?
Blynk.run() needs to be in the void loop() at the very least… it is Blynk’s housekeeping command and basically keeps everything running. And since it is in the void loop() which already runs hundreds or even thousands of times a second, there is no need to “defer” commands until it runs.
As for all your Blynk.virtualWrite() commands (and all other Blynk commands), they are supposed to process immediately by the library,if not directly by Blynk.run().
If you want “deferment” simply code in as such; As you have already indicated that you use timers, this should not be an issue. And estimating command process timing and thus ideal timer settings is part in parcel with learning to properly code in the first place. You could even use milis() and Serial.print() commands to determine exact start and stop times during code development.
That said, sending out “lots” of commands may not be an issue anymore, as such appears to be now automatically regulated via the new 0.5.0 library.
Hopefully this clarifies it for you… 
If you are still unclear on something, please ask.