Oh I think he understands.
This really doesn't work the way you think it does. The display driver knows the rate of change of the content before it pushes the content to the display itself. It's going to set the minimum refresh rate needed to display all changes in the content it's sending to the display. There literally will be no dropped frames. If the rate of content change is only 10 frames in a second, the display will drive at 10hz. If the content over the next second suddenly has a much higher rate of change, say, I dunno, 107 times, it's going to drive the display at 120hz. If it's 58, it's going to drive it at 60hz. There is no "catch up" problem as you seem to be thinking; the display subsystem knows the rate of change of content before it ever gets pushed to the display.