So the cpu blockers almost never run under normal use. I believe this approach is a good tradeoff away from code complexity. In MXT systems the memory is overcommitted. As I stated before, there exists X amount of memory in the system but the system runs with 2X the address space. Therefore, swap space must exist to cover the worst case.
Disk space is cheap.
In conclusion, the MXT support patch and driver help keep the compressed memory utilization down when needed. The discussion on cpu blockers, eatmem threads and swapping overcommitted memory might have given you the impression that there is an ongoing fight to keep the compressed memory utilization down. However these do not happen during normal use. Most applications are compressible by a factor of 2 or even better. The MXT driver code almost never gets activated.