I do. For a couple of reasons.
Over time Asobo’s code gets better at catching poorly written routines. For instance back at SU2 or something, they got better at catching errors in the manifest.json and people were wondering why their packages weren’t showing up.
Also, the content.xml file can get “messy” over time as new packages are added and it’s not sorted.
So, to make sure the base installation was installed properly without having to deal with errors in my Community Packages, and also to “reset” my content.xml, yes, I like to rename my Community directory and create an empty one. That way the content.xml gets rewritten at the bottom end, and I can test my base install without interference from other packages. And then when I reload my Community directory, it all gets sorted again and rewritten afresh.
Sadly, Asobo / Microsoft (I don’t know who), chose to put Marketplace purchases in the base install, and made it super difficult to “turn them off”, and they also can be rife with errors. I understand there’s a difference between how Marketplace packages and Community packages are handled, but I do wish there was a “Marketplace” directory like the “Community” directory so they were more easily managed.
Every time I load packages I have to check them for errors. Because the code is so poorly documented, soooo many developers use the VFS improperly and cause problems with the software for instance. And there are lots of other errors, too that happen. It’s a wonder why there aren’t more CTD’s people experience.
I hope someday soon, too, we get better content.xml management and it fully allows users to sort ALL packages, instead of just OneStore packages, and then Community packages, as well as turn things off and on more easily.