I think the whole system you’re setting up is trying to solve two things :
First a simple way to copy-paste trees without sending a complete blend file.
Which sounds like a very needed feature, the fact that your addon is in the official repository is also a great first step for it to become more standard.
Then what you’re doing here is like a repository for nodes which is very similar to what NukePedia could be : https://www.nukepedia.com/tools/gizmos/
Which in itself is amazing, having a centralized place where you can look for nodes that are easy to append in blender is very cool !
But I think this is something that should be officially backed by BF, or at least you should have their input on that. If it’s officially backed then a lot of people is going to use it, and it will become very useful as the place to go look for stuff. Just like the extension platform is currently useful.
Anyway, I think the clever thing to do would be to get in touch with Julian Eisel who works on assets and see how what you’re doing here could align with blender. Then if nothing can be done at least you would have tried But we can say that both problem you’re trying to solve are two thing that would benefit blender in the long run and is aligned with other DCC so it make sense !
In the short term what you’re doing is actually already useful as it helps design the tool and narrow the need.
But the more useful this is going to be, and the more used it will be , the more official it as to become !
anyway, that’s just my two cents, next time I have to work with node within a team I’ll definitely try it out !
But we can say that both problem you’re trying to solve are two thing that would benefit blender in the long run and is aligned with other DCC so it make sense !