The agility argument is a good one, for sure. I for one don’t think any of this non-destructive workflow stuff would have happened if we had left everything up to the VRCSDK 
I think what’s key is finding what commonalities exist that are:
- Tricky to implement correctly
- A source of compatibility issues or user confusion
- Duplicated across multiple tools
One such area that comes to mind is the Apply on Play processing that has been a problem lately - we’re just recently getting to a good common ground, but - fitting into the discussion about how it would be nice to have an officially blessed emulator - having a common mechanism to trigger these avatar processing hooks in play mode would help a lot for maintaining compatibility with other build plugin frameworks. That being said - please do reach out to Senky and I if you do start implementing such a thing - there’s a bunch of really subtle pitfalls there, and getting it wrong would be worse than leaving it as is! (I’m still not entirely sure we’ve got it right, for that matter…)
Regarding the “promote” step of “love, promote, support” - I posted over on the tool creators forum as well, but it’s really unclear what the criteria for entering the curated packages list are currently. Certainly nothing has been added recently… Or is there something else you’re thinking about for promotion?