Thanks to all who tested your surround plug-ins. 
Since I just have it open in a project, I immediately took screenshots of NUGEN Halo Vision (v1.0.1.1):
Unfortunately a NUGEN plug-in that does NOT work correctly. 
And here is LiquidSonics Cinematic Rooms (v1.2.0):
The program only distinguishes between “front” and “back”, but this works CORRECTLY.
Interesting. The newest plug-in in the range of NUGEN unfortunately does not work correctly. (See above .)
I would not rely on the information in SuperVision. I have already found that there are circumstances where the display does not match the final Atmos mix.
Dolby Atmos is always 9.1.6 in the home theater (i.e., at the consumer), and that’s how the signal is processed by the Atmos renderer. (No matter what Nuendo displays.) The renderer only stores the metadata of an object anyway. And aside from the LFE, Nuendo also converts a bed into objects. The Dolby Media Encoder (DME) or the Encoding Engine (DEE) always distributes the metadata of these objects to a signal with 16 channels (9.1.6). This is the maximum for Atmos in home theater. (Dolby Atmos is only truly object-based in cinema playback.)
I have opened a separate thread on this topic here in the forum. In it I am also concerned with such things. Unfortunately I haven’t found the time to write more about it yet. Maybe we should move the topic there or open a separate thread.