All,
After the hosts were upgraded, they never fully connected back with the managers and the NSX bits had references to 6.7-3.1.0. Applying the profile that was originally created in 2.5.1 would not upgrade the hosts and trying to list the Transport Node Profiles with a general error.
See below for the blog article on how to get around this.
https://blog.clearpathsg.com/blog/nsx-t-2.5-to-3.0-upgrade-error-fix