If I read you well, you're suggesting WP H&SEP for single sites but WP HG for multisite environments.In multisite with several templates installed, each one including the childs must have its own mapped name.
For example: If you have a site with 120 installations and about 80 different templates each one must be mapped with a different name.
The same with the style sheets, each one must have a different name including the child.
For 1 site it is fine, but for a medium to large scale multisite without extra development work, it is a big problem.
Another negative point: This plugin is not compatible with PHP 8 (8.0.7), throws error, cant be activated.
Removing these problems is an excellent choice.
Wp Hide Ghost: 1 same configuration is replicated on all sub-sites.
It is 100% compatible with Wp Rocket (https://docs.wp-rocket.me/article/854-using-hide-my-wordpress).
Anyway, if this is not a problem for you, WP Hide & Security Enhancer PRO is an excellent option with much more robust options.
This is interesting. Let me explain.
Since we all are dealing with a fine line in regards to GPL, no names will be used.
We run a multisite as storefront for a single site business. They can select the template, option, what-nots and we copy & install the subsite into a single site. Managed or unmanaged.
Up until now, we've been using WP HG because, as you mention, the ability to export the config across all sites.
Now you're saying it would be better to apply WP H&SEP to single sites?
Es decir, mejor usar WP H&SEP en nuestro multisite pero cuando un cliente pide que desenganchemos su sitio y éste pase a ser single-site, entonces usar WP HG. Es correcto lo que sugieres?