I don’t see the use case. Yes, it is a lot of configuration but the functionality is there already. You just have to build out your core workflows and objects to show what you want, how you want it. For instance, my tree select has 30 items, which each have sub-items and so on. Because Type-Subtype-Subtype, all falls under the same tree, I can just have that “ITIL type” object. When I setup my object, I use ITIL Type:“A”, “A.1.”“A.1.a” and have the preceding levels also in the text of each sublevel. This way I can do advanced searches and still see what I am looking for without creating tons of objects.
You can also remove/hide objects from your selects in your core workflows. So if you have a select with Type:(Hardware, Software, Network,etc.), then create a select Subtype:(Hardware>Print, Software>Microsoft, etc.) then another select for the next level and so on. Then youd setup several core workflows for when selected Hardware, hide all the Software and network subtypes, and so on.