If the randomTickSpeed game rule is set to a high value (but not high enough to cause MC-76117) and then to a very low value (like the default 3), the game sprints for 1-2 seconds and then goes back to normal (delaying every tick when necessary to match the tick rate).

How to reproduce:

1. While in a singleplayer world or a server where you are an operator, press F3+2.
2. Run the command /gamerule randomTickSpeed 50000 and observe the graph at the bottom right of the screen.
3. Run the command /gamerule randomTickSpeed 3 and observe that the game doesn't delay ticks to match the tick rate for a few seconds (the graph at the bottom right doesn't show any green lines above the red lines of each tick).

Expected result:

The game is not lagging anymore, so ticks would be delayed to match the tick rate.

Observed result:

The game sprints for a few seconds and then returns to normal.