I uploaded a
quick encode of jlun2's run.
So jlun2's run collects that one red cube at frame 1512 (1:24 in the encode), while the OP collects it at
at least 1522 (though it is off-screen). It looks more like 1524, but anyway, it's at least 10 frames slower than jlun2's.
Then, the tables turn. While jlun2 takes the very long (intended) route over and around to the floating pairs of brown blocks, the OP bounces up there early by walljumping on the same wall multiple times. At the point he bounces on the first floating pair of brown blocks, he is exactly 256 frames
ahead of jlun2. Then, by the time they both touch the gray cube at the end, he has gained 3 more frames on jlun2.
So while jlun2 may be faster for half his WIP, his movie cannot be verified to be faster than the OP for the second half because of that big missed shortcut.
Also, both movies ran fine up to the comparison point (I got a desync later on in OP's movie just like everyone else) on my Windows 7 64-bit computer with only changing Multimedia Timer Mode to Asynchronous.