That was an old topic… Blynk later added in some form of ‘governor’ to the library that keeps flooding from happening at the expense of loop cycles.
So rule no exceptions… The warning is still valid, as that is just bad Blynk programming form. And the results, while still there, are just not as cripplingly noticeable.
PS I moved your comment to it’s own topic.