Anyone in test for the domain able to attest that formal USB compliance verification would have detected the design defect that this hack resolves?
If you need this fix, it will literally refuse to work with any spec-compliant USB-C device on the other side of a C-C cable. No way to miss it.
In practice, most if not all networking/hardware department carries a ethernet cable tester but somehow not true for USB cables.
You don't need a cable tester to detect this problem; just plug the device into a spec-compliant USB-C power brick with a USB-C cable and see if it fails to charge.