FYI, as you have been informed and has been referenced many times by @Pavlo himself… Ideas and suggestions for future Blynk are now requested and prefered to be sent to the roadmap. This helps keep them in one spot for developer reference and a degree of community voting to assist with judging actual community interest vs a small group or individual’s unique desires.
https://portal.productboard.com/blynk/tabs/2-all-your-ideas
Meanwhile, you are assuming that the server reacts differently when multiple SAME vPin requests happen as opposed to multiple DIFFERING vPin process occur. I highly doubt that is the case as Blynk’s protocol looks virtually the same for each and every process. Flooding is simply a case of too much too fast, and the needs for the governor are also dictated by the Cloud Server and it’s bandwidth costs as well as IoT infrastructure as compared to Local Server and user’s internal network environments.
If you want faster, ungoverned transfers, use a Local Server and the #define BLYNK_MSG_LIMIT 0 command as listed here
This all said, if you have actual code, library contributions and/or “solutions to issues”, perhaps the proper venue for submitting them is Blynk’s various GitHub repositories instead of creating multiple topics that slowly fade away into the queue.