Firstly…
Why is this Blynk’s responsibility? Reading such impulses has nothing to do with Blynk.
Rather, one would use already existing and varying interrupt & counter code, along with whatever formulas needed to break it down into RPM or RPS, etc., as used in many Arduino projects floating around the web. See here for example - Arduino Playground - ReadingRPM
Blynk is predominantly an IoT GUI, thus can already easily be used to take the resulting values from aforementioned code functions and display it across your IoT needs.
Secondly…
I would recommend keeping the function called from the interrupt as lean as possible… just a simple counter increment will do.
Then using a timer controlled function, you can call up the counter value, run your calculations for the final displayable variable, send it to Blynk’s App, clear the counter and carry on.
For example on the final stage…