I ran this fix early on and had mixed results. It's a good code and well intended.
After working with this switch, I ended up removing the link and going back to a neutral setup.
There are lots of "cures" floating around that may provide temporary solutions to the ORBX/P3D v2 autogen display anomaly. None of these will address the core issue, which is being worked on by the ORBX team and LM.
I'd wait for the approved installers to come from ORBX and avoid integrating any phantom code(s) into an architecture that is already highly complex. Once the OEM code is approved the temp fixes will not be needed and possibly could create new conflict.
IMHO.