Non-availability of certain modules in Edit Mode to complete default web-blue-template

If you install a fresh new virtual site based on the web-blue-templates, you start from a nearly virgin core template that you have to populate on your own in Edit Mode. However, just by trying to redo the default header of the ACME site as an exercice tend to rapidly get complex as some modules are not available in Edit Mode.

For instance, just adding a lang switcher to your newly created site from the Edit Mode is not possible without having to go in the Studio and redeploy the web_blue_template (which will override the ACME?)

Would be nice to deliver default "virgin" template set with:

• either the default header/footer elements in place (but editable if the editor wants to change them later on)
• or provide the modules in order to let the editor redo something similar to what exists in the ACME import package.

Currently the editor has to install an ACEM site and copy/paste the header into his newly created virgin site. This is also quite strange as unvailable modules in the Selector are copied and instantiated without any problem (e.g: search module or lang_switcher). So should not such modules which are in all the cases present and usable by simple copy/pasting from ACME be also available through the Selector? Or, if only available from within the Studio, to ensure that the "Editor" can not access and reuse them even trough copy/pasting of objects?