Amazing! Thank you for this, I’ll take a look at the queries, BlitzIndex has revealed an awful lot. The server is bounce monthly to apply patches.
Rebuild generally fails as it cannot get a lock on the index, if you have SQL enterprise it can build them while online. I do run it on occasions during the day but it’s a rarity than the norm as it’s ran once on th weekend. And with SSD fragmentation is less of an issue than it used to be. The stats are arguably more important along with checking on the hit to update ratio on any index you put on.
Not sure on the Ola stuff. We have never really ran into SQL perf issues since 2005. And that’s just adding in about 4~ of our own indexes. The biggest downgrade was the Cardinal estimator for SQL 2012+.
No Worries mate. You have probably clocked it but when you do any of this you need to get the query stats against your live systems and you want it to have been up and running for a few days so the SQL server has had time to generate the best dataset. FYI we use simple recovery model on our SQL server too so its not bogged down with logs.
Incidently this is the results I got with Claude using the above. Some awesome users_seeks to user_updates 
Enabling Query Store on your database can provide a lot of valuable information as well:
I find particularly useful for identifying queries that have regressed due to query plan changes.