Best practice with "Blynk.virtualWrite(Vxxx stuffgoesup);"

[PeteKnight]

First of all, you need to be careful about your timers.
16 is the maximum for one BlynkTimer object, and you need to set them up so that they don’t all try to get called at the same time, and that if some have longer cycles then a number of timers don’t all coincide at one point (every minute for example).

The “Staggering Timers” section of this tutorial explains more…

Using BlynkTimer or SimpleTimer

Many users seem to struggle with the basic concepts of using BlynkTimer in their projects, despite the excellent discussions and tutorials that exist on this forum, so I thought I’d write a guide that will hopefully help clarify things. It’s rather long, as it attempts to explain the reasoning behind why and how we use timers, and covers some more advanced subjects, but I’ve tried to organise it in a way that helps people to find answers to specific questions… Why use a timer at all? Let’s say …

As far as your original question is concerned, you’d be better keeping the Blynk.virtualWrite commands in their individual timed functions.
Blynk doesn’t like it if you try to push too much data out to the server at one time, and the preferred limit is 10 write events per second, so trying to do more than 10 immediately after each other isn’t a good idea.

Pete.