Auto-populate Virtual Hue/Sat parameters on Fixtures with 1931 CIE x y Profiles

There were a ton of feature requests to connect a fixture's native x y values to the color picker over the past few years and I'm so happy that finally happened within the past year or so (I think v3.0 and up?). However, I believe the color engine's capabilities aren't being utilized fully. 

When you create an RGB fixture, the profile automatically creates virtual Hue and Saturation parameters making assumptions about the Color Space/gmaut and not being very accurate - that's unavoidable and understandable. But it gives you those virtual channels nonetheless, along with full control of the color picker - again, even if not accurate.

When creating an x,y fixture, (cie 1931), the color picker is now tied into the fixture's x,y parameters allowing you to use the color picker (as CIE xy, Gels/Swatches, OR as Hue/Sat) with those x,y fixtures and NOW you CAN get accurate results. (Hooray!)

Yet, when creating an xy fixture, virtual Hue/Sat parameters don't automatically appear. I tried to add virtual Hue/Sat parameters to those x,y profiles since Eos is doing those calculations anyway in the color picker but the moment I change the DMX to "Virtual," the parameter disappears.

It appears that virtual color channels (like Hue/Sat) are only reserved for fixtures with RGB parameters. This is a major letdown since very few RGB fixtures have given ETC accurate calibrated, color space data to make those virtual Hue/Sat parameters useful. Yet, x,y fixtures don't need to provide any data to ETC since x,y 1931 color space is universal.

Some fixtures may not be able to hit certain satuartions but in that respect they also can't hit certain x,y values and you can still dial those parameters to those values. (usually the fixture just remains on the vector from the edge of the gamut to its set white point and gives you a desaturated version of that x,y point.) Giving a virtual Hue/Sat would work the same way and shouldn't be an issue here.