Beautiful work Condac.
Thank you for clearing up all of the murky data that Futaba was giving.

So in summary thus far we have:
-4PX is roughly equal to the M12.
-4PX Minimum latency stilled turned out to be around 2.2ms - 2.1ms (race mode); even though it was calculated based upon Futaba's unreliable data.
That's still better than some of Futaba's data that was originally pointing towards 2.7ms - 2.3ms.

-M12 still has a slightly better Average Latency spec (4.1ms vs 4.6ms)
-M12 uses the highest theoretical frame rate of 384hz vs 4PX of 333hz which may be helping to tighten Average Latency specs.
-M12-S & MT4-S will be faster than 4PX in both latency and frame rate
(Any way we can get you to test both of these Condac?)

-Fasst Rx is faster than SFhss both in Frame Rate and Latency.
-TFhss (big surprise) is faster than Fasst in Frame Rate and Latency.
-Telemetry hurts Average Latency (at least for Futaba).
-4PX Frame Rate and Latency are affected by the Rx that is used.
-Rx Frame rate and latency are more key for the 4PX than Rx resolution.
-Frame rate has a similar impact upon servo control (connectedness) as resolution has been debated to have.

This is why we test: Based upon this independent test data I was able to test a different Rx and found a substantive difference on the track with car control.
For me, car control = "connectedness", instead of "responsiveness" alone (although I do think that it IS important; which is why I have everything maxed out on my 4PX ).

We wouldn't have known any of this for sure Condac without you. Thanks again. Now, get a hold of an M12-S, MT4-S, and the new 7PX when it comes out, and show us the data.