Thanks for your bug report. As mentioned by maroon, this issue has been discussed before. This is not a bug and is by design. This feature was added to v5.91 in 2001 because a scripter requested it. It is likely that the scripter wanted a way to temporarily stop a timer command from being triggered but still wanted it to continue counting down. At the time, calling it "pause" probably seemed reasonable, since it paused the triggering of the command, and that is the context in which we understood it.
I have updated the help file description to make it clearer.
