Every feature has a technical debt. This feature, the ability to visually compose all options of a blueprint, is no small feat. I’d imagine it would add some debt. Maybe that’s a larger install size, more server resources to run this particular feature, additional documentation, potential security risks, potential compatabilty issues, etc.
The more you have, the more you have to maintain. Every time Kirby has some blueprint enhancement this feature would need to be worked on, documentation updated, etc. That’s a lot of time invested for the Kirby team. And for what, the ability to compose blueprints which is already possible? I’d rather see time invested in improving my end-product to the client, the best content managing expierence possible.