Measuring the time between a simulated keypress and pixels changing in the framebuffer seems kind of inadequate, since it’s missing out on delays in the input and display hardware.
It would also just be nice to know the magnitudes. If the hardware adds a constant 100ms (for example, not a real number) then a 10ms advantage on the software side looks less interesting.