Metroman and why is frame counting is a bad way to scale

Disclaimer: This post does not support either side in this feat discussion and I am not the schizo with their alt account.

TLDR: Frametime scaling does not give an upper limit of how fast a feat could have happened, only a speed floor (which is not even the slowest possible).

So, why is media framerate counting a bad way to scale:

People in other threads used the movies framerate of 24 fps to measure Metromans speed feat of being out of sight for one frame. The problem with this is it ignores the moments between the 2 distinct frame time where the picture has not been updated because of framerate.

Think of this like this:

Frame0: Metroman visible Frame1: Metroman gone Frame2: Metroman visible

F0-------------------F1-------------------F2

When Metroman disappears on Frame 1 (F1), we dont have information WHEN did he started moving between F0 and F1.

F0---|----------------F1------------------|-F2 Here ? F0------------------|-F1------------------|-F2 Or here ?

Its a 1/24th second of difference, where in the slowest case he was gone for almost 2 frame worth of time. Its not much a difference in the slowest case, but lets look at the fastest case:

F0-------------------|F1|-------------------F2

In this case the time he was gone can be argued to be as small as you want it to be as long as he is gone before the frame update and only comes back after it.