Except applications don't tend to lag "for ten frames", but for "ten ms". Your application that skips ten frames at 100 Hz will skip a hundred frames at 1 KHz.
It's true that some applications have input lag due to simply being slow to process input. But there are many applications that actually process input fast enough, but still have a lot of input lag because of various forms of buffering linked to frames. A typical scenario would be 1.5 frames of latency due to the desktop compositor, 2-3 frames due to buffering in the graphics API (graphics APIs optimize for throughput instead of latency by default), and 1-2 frames because the application state doesn't completely update on the same frame as the input is received. Ten frames would be unusually bad, but it can happen. It all adds up! And all of that is made faster by higher frame rates.
Properly made applications can bypass most of that latency but few bother to really optimize for it, so a systemwide fix is welcome.
