Have you tried to set to rate limit fractions of second like 0.1 for example?
Take into consideration that you need to select the option of "drop intermediate messages" otherwise the messages coming after are just delayed.
From other side consider node-red is not a real time system and depends on processor availability etc.... so working with very low precise times is not the goal and will be more reliable depending on the application to let this to work on an arduino board for example that you can control with node red.
All depending on real needs....
I want to point you one thing that is important to realize.... is not the same:
- Rate limit 1 message every 250 miliseconds
-Rate limit 4 messages per seconds
I can explain you better but most probably you already see the difference. The final result on the behavior will be slightly different, have it on mind.
In the example you show suppose the case you are reviving a message every 0.1 sec, what will happen is on first second you will see coming out the messages emitted at 0.1,0.2,0.3 and 0.4 then nothing and after first second is over you will see coming messages emitted at 0.5,0.6,0.7 and 0.8.
If you select intermediate messages drop when first second is over then you will see coming messages emitted at 1.1,1.2,1.3 and 1.4.
This is not the same that allow only 1 message every 250 milliseconds and drop intermediate ones.