Delay node set to rate limit omits messages unexpectedly in case of bursts

A similar question has been raised before, without a final answer. I think what you see is the result of how the delay node is designed to interpret "rate limit." A rate of (x messages per y minutes) is interpreted as 1 message every y/x minutes. Regardless of how many messages are received, they will not be transmitted less than y/x minutes apart. You can select x and y however you like, but as long as the ratio is constant, the result will be the same. There are other ways you could interpret "rate limit," but this one was chosen, and it is as reasonable as any other.