I think the ability to disable/enable VSTs would also be a great feature.

One case I could definitely use would be to batch enable or disable VST2 plugins.
I always use VST3s but sometimes I receive projects to collab, mix or master which use VST2s so I would only enable them then.

 

As long as the data can be imported and exported as a table, and not in some proprietary file format that works with nothing else; you could do whatever you want with the data and bring the results back into it. Instead of trying to get all the details from the actual plugin files, it could auto-fill any details you want from an online master file. Like how an application can fetch one of the firewall ruleset blacklist subscriptions via github, or the dynamic updated nativeaccess.xml. Or auto-populate the table using AI to do all the lookups in various columns.