### Current Behavior
When the delay node is configured as.
- Rate Limit
…
And
- No messages are currently held back.
Messages containing `msg.reset` are being passed through
### Expected Behavior
It appears this is new behaviour, and previously, `msg.reset` has never been passed through, as it should be a control message.
I'm unsure if this is now expected behaviour, or something has gone pop!
### Steps To Reproduce
- Set Delay node to `Rate Limit`
- send it a message with `msg.reset`
See that it passes the messages through.
### Example flow
```
[{"id":"847f3a065f5f8cdd","type":"tab","label":"Flow 1","disabled":false,"info":"","env":[]},{"id":"b0f341d4815fa7ea","type":"debug","z":"847f3a065f5f8cdd","name":"debug 4","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":1115,"y":100,"wires":[]},{"id":"a4a9b730b905294c","type":"delay","z":"847f3a065f5f8cdd","name":"","pauseType":"rate","timeout":"5","timeoutUnits":"seconds","rate":"1","nbRateUnits":"1","rateUnits":"hour","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":true,"allowrate":false,"outputs":1,"x":910,"y":100,"wires":[["b0f341d4815fa7ea"]]},{"id":"351578f6dd252a3f","type":"inject","z":"847f3a065f5f8cdd","name":"reset","props":[{"p":"reset","v":"true","vt":"bool"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","x":680,"y":220,"wires":[["a4a9b730b905294c"]]},{"id":"c944b4bae18a02ea","type":"inject","z":"847f3a065f5f8cdd","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":680,"y":100,"wires":[["a4a9b730b905294c"]]}]
```
### Environment
- Node-RED version: 3.1.0 (but I cant help thinking I noticed this change a little before)
Not at my workstation currently, but this is discussed below also:
https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221
