On top of the SQL checks, I would be doing a chkdsk on the system as well. Don't want to find out that the physical disk (OS and SQL disks) have problems on them. OS's generally don't like unexpected reboots, so ensuring the OS is happy would be good too.
Might not hurt to check the OS logs too to make sure that there are no odd errors in there. Even if SQL is running fine and error free, if it is running on an OS that has errors, you may be asking for trouble...
I'd also be checking to make sure the backups are still succeeding (tlog, differential, full on the SQL side and get the VM team to check on the VM backups). They likely are, but doesn't hurt to do a quick manual check. I like to double check things like that after unexpected reboots just to make sure that everything came back up properly. We use RedGate SQL Backup at work (for example), so after an unexpected reboot (and usually with an expected reboot), I double check that the RedGate services came back up properly.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.