I get that it is possible to describe some kind of rule set which will allow you to achieve a degree of control/visibility over admin access, but having these sorts of hardcoded rules is somewhat antithetical to the Fibery principles (flexible, open platform, upon which a number of use cases can be built).
Overall, I would strongly encourage you to think about what you can achieve by having as few workspace admins as possible (ideally only one) and not using an admin account for every day tasks - only on the rare occasions where creator access in the relevant spaces is not sufficient (e.g. inviting/managing users).
The admin account(s) need not be tied to a single person (and you could even require minimum two people to be present when logging into the user account, perhaps with decentralised partial password access). Maybe the company can have policies for submitting requests for configuration changes to be carried out under the auspices of the workspace admin account.
Overall, I think there is more chance of this feature being implemented, combined with notifications to specific users when the toggle (to “admin mode”) is enabled.