Answer
Technically this can work by maintaining a separate ifsroot folder structure per environment and switching the KUBECONFIG context every time you connect to a different cluster's environment — though this isn't confirmed as an officially supported configuration, just a technically workable one. There's an undocumented helper script (set_remote_envs.cmd, in the installer folder) that sets KUBECONFIG and the default namespace automatically for a correctly-structured ifsroot, but it comes with no error handling or official support, so treat it as a convenience shortcut rather than a guaranteed-reliable tool.