Modular Nested Experiences with Dynamic Referencing Support?

We have a large international client that has many products under different departments. In order to meet our client's needs, we are working on a solution where they can have multiple experiences (one for each product) that can be modified by admins for content localization and information access. These need to be loaded into a parent experience that showcases all of their products as a complete solution which admins can independently control, e.g. to block and permit access to specific products by region.

They need to control the child experience to be able to modify text per region and add new products without having to completely update the full experience at the developer level.

They need to control the parent experience to be able to show how products relate to each other, hide products that aren't sold in certain regions, and dynamically load new child experiences that are added into their product lineup.

Having a large, single experience is not an option due to the amount of products and departments they have, the inability to add new products, and the large amount of marketing copy, videos, and images for each one would make the single config.json file either too complicated for admins to organize or too deep for Showpad's Admin UI to parse.

Is there a way to reference an experience into a parent experience just like any other content and control which references are available through the parent's config.json file?