Worked with vmware support today. The tech suggested that we could workaround the issues by "silencing" the health check alarm and creating a custom baseline in VUM based on importing the ESXi ISO image file. I responded by pointing out that the workaround does not address the issue of the vsan release catalog db file being populated with invalid data and that we should first fix that before attempting any workarounds. After all I had previously already done just that so I could upgrade from 6.5 to 6.7U1. He checked with someone at vmware and decided to check internally with his team to see if a new json file with the correct and current ESXi version/build number data is going to be released any time soon.
For those that are talking to vmware tech support feel free to reference my support ticket : 18973209311. Also please submit feedback on the kb 58891 to encourage them to update the release catalog db file with current release versions and build numbers.
Cheers,
Ron