"noframemerging" in Edge is not supported

The use case is -

(session 1) An end user is logged in to our application in Edge. 

(session 2) The user launches one of our desktop applications that requires another session to be created at the same time.  Note that multiple of these sessions could be requested at the same time too (user may launch the desktop application one or more times before exiting from the prior session)

(session 3) The user performs an action in Edge from session 1 that creates yet another session.

Session 2 and session 3 are short lived meaning the user could be in and out of them multiple times while still active in session 1.  It's important that all of these session do not merge to allow the user to continue to work without needing to re-login to the application.  And also, to allow user to perform above actions in parallel.

Currently, the application code launches session 2 and session 3 in Internet Explorer programmatically with the -noframemerging switch to prevent merging this new session to an existing session.  But since this option is not supported in Edge, it seems to leave us with only one option which is to utilize Edge's Profiles feature.  And the way I envision that would work does not appear to be a clean solution.  It introduces an additional step of profiles creation for the customers (users and their IT department); something that they didn’t need to do in IE.  In addition, users would always need to open an Edge session (session 1) in a specific Edge profile, that is different than the profile that will be launched programmatically from session 2 and session 3.  This could be messy - let's say there are 3 Edge profiles created, named Session1Profile, Session2Profile and Session3Profile.  And, users are instructed to launch an Edge session in Session1Profile.  Session2 is launched in the Session2Profile from the desktop application code.  And, session3 is launched in the Session3Profile.

My concerns are that -

1. It's not guaranteed that users will always open an Edge session (session 1) in the Session1Profile.  This is something that application developer has no control over.

2. Hardcoding of the profile names in code for session 2 and session 3 workflows.  The names can be config driven but still have to be known to the code.

3. Since there could be multiple session2 sessions, what can be done about that so that they don’t merge with each other and also to other types of sessions?

VBScripts and ActiveX

Ideally, the expectation is that the -noframemerging support gets added in Edge so the use case described above continues to function in Edge.