There are a few places where the MCO checks if a FeatureGate is enabled. We are handling error differently, in some places we return the error back to the caller, in others we just log it and in some others we ignore the error.

Based on the code of the FeatureGate retrieval logic, the error the function returns  can only happen if the caller is checking the FeatureGates before the logic gathers them for the first time, after that the error cannot happen. 

If we centralize the handling in one single place, that ensures FeatureGates are retrieved (we are already doing that at boot time) and wrap the logic inside our own common FeatureGate retrieval logic we can simplify the way we check for them and avoid dealing with the returning error in every place we need a FeatureGate.