Yes, Everything could handle all three much faster, but there are a few things to consider:
- Everything's SDK3 should let you do this really easily with a single query. The bad news is that Opus still hasn't implemented it.
- With the current SDK, it would only help with enumeration, which would only be useful for case 2. But then you'd have to process potentially a huge number of paths, which would slow things down on deeper folder structures.
One thing you can do is use the CLI version of Everything, which does support SDK 3. I actually use it in another script to grab certain properties from Everything. It should be fast enough because in most cases you should only need to query once. The main issue with that approach is that you don't have a reliable way to tell which items are expecting values, as discussed here without a solution.
When I have time, I'll check the best way to include the Everything CLI and blend it with the current work here (or if it'd be better to keep it in a separate script). Since I'm not the main audience for this script 
, I keep wondering what the real use and purpose of that data is inside Opus. It feels pretty niche to me.