Sure - though some of it depends on what the final solution could be:
As a hypothetical example which sort of represents my client's requirements:
. Start with a portal that has standard navigation, and we need to replace ESS and MSS with an ESS launchpad and a MSS launchpad to keep it inline with the other navigation.
. Once in ESS, they should have full personalisation functionality for ESS tiles, but no access to non-ESS tiles.
. Same applies for MSS.
e.g. We need to ensure ESS launchpad remains focused on ESS and MSS, focused on MSS.
If thinking about mobile users, we would probably deploy a single fiori launchpad page that has ESS and MSS contained within it per how it is designed to work.
Let me know if that does not paint a clear picture,
Matt