Bug Audio Mixer Exposed Parameter Inspector Performance

I'm working on a project that involves mixing a large number of exposed parameters (245) from different mixer groups together, and the performance of having exposed parameters seems to be O(n²) with a pretty high n or something; it tanks the performance of the inspector. Simply renaming an exposed parameter takes around 2-3 seconds per keystroke.

Am I abusing this system in some unexpected way? It seems perfectly reasonable to have several groups with exposed parameters.

Below is a profiler snapshot of the editor when highlighting a variable name:

 

Same here. We're working on an audio app with 24 channels and lots of send routing + helm synths.

So far I am at channel 10 exposing parameters (1338 and counting) each time I wanna expose a parameter I need to wait around 5 seconds for the parameter list to refresh.

By the time I'll be on channel 20 I will need to wait 10s each time I wanna expose a parameter.