Reduce harmony patch overhead

[Owlchemist]

Lots of VFE mechanoid patches are running even if you don't use that mod. Regardless of how lightweight the patches themselves may be, they would still add detour overhead to the methods of which are running constantly.

• These changes gate the patches to only apply on game startup if relevant.
• Added a check to see if the mod is active and applied it to other checks throughout the code that do the same, to unify it.
• Also a small optimization to ModCompatibilityCheck's startup impact

It may be good to have Taranchuk sign off on this one as, afaik, those harmony patches belong to him. I skimmed them over but as far as I could see they would be fine to omit when VFEM isn't active.

[Taranchuk]

The thing is that not only VFEM mod uses these mechanoid patches, but also RimEffect, Reinforced Mechanoids and Mechanoid Foundry. The code was put into the framework for a reason otherwise would stay in VFEM where it was created initially.

[erdelf]

We might be exploring other ways to lessen the load in the future, but this for now doesn't work, as taran explained.

[Owlchemist]

Would just checking to see if a CompMachine exists anywhere in the database work as a new gate?

[Taranchuk]

Could work this way.

[legodude17]

Maybe instead of doing the flat mod presence check you could have CompMachine and Machine set flags on load to apply the patches?

Edit: Yeah basically what you already said.

[Owlchemist]

Sure. I can just redirect the bool to point to that logic instead, then.

[legodude17]

Maybe move it out of ModCompatibilityCheck, then. Since it's not really a mod compat thing anymore.