Most things within the console used cashed results for performance reasons. If you are looking for troubleshooting then resource explorer is always uptodate.
How often are you doing HW inv? What about Heartbeat discovery? In both cases, I recommend these be set to daily. https://askgarth.com/blog/inventory-cycle-version-numbers/
I have not looked that their scripts but my guess is they use heartbeat discovery data. I personally don't add collections for the sake of having collections. I only add them when I need them. Why because this adds overhead to your site server and can slow down everything.
If the data is based on Heartbeat discovery, triggering HW inv. will do nothing to make it fast. You need to trigger heartbeat discovery. Don't forget that the collection membership need to run too before the collection will update. And you will need to do all collections aka limiting collections too.
To echo the infamous words or Jason Sandys there is no such thing as Best Practices. And he is right, there is only the things what work for you.
BTW I'm assuming DC = Device collections.
I 100% agree with Sherry Collections are NOT for reporting. SQL (Reporting) is for reporting.
There is even a built-in report for OS details. Have you looked at them?
I'm curious, what setting will you have different between Windows 10 versions? as it clearly sound like you are using collections for reporting and it will slow down your environment if you are not careful.
Although it is not until May, I would ask to go to https://mmsmoa.com/ this is the place to learn more about ConfigMgr for Experts (like @Sherry Kissinger ) :-)