No, I assume the real reason to be the fact that many extensions need to be adapted to mobile as can be gleaned from the non-appearance of the 'More options' page in PrivacyRedirect. Mozilla just chose a rather clunky and ham-fisted way to keep untested extensions from running on mobile. They could have added a simple option to allow untested extensions from the standard repo with a disclaimer of such a configuration not being supported.