Downgrade to 8.6...
So what you want used to be the behavior until 10.0 when they changed it to roam across groups. To do this in 10.0 and higher you need a new personalization instance. You need a second db which can be on the same SQL server and a second personalization instance which can be on the same personalization server using a different port. In em policy pre-session evaluate conditions and then assign the personalization server there via admx actions. It's definitely not as easy as it used to be but can be done.
Ufff! I have to think again. Don't know if this is worth the hassle.
I hate this feature of Environment Manager 10.
In our environment we always had a couple of Personalization Groups for different things. E.g. Troubleshooting, Pilot, etc. and we could just move users around as we needed to. Unfortunately this no longer works. The way we have worked around it is by cloning the application groups and having, as an example, Office 2016 Production and Office 2016 Troubleshooting.
Its a horrible workaround but its allowed us to not be forced to build an additional environment for this.