Hi Michael.
After spending two weeks troubleshooting this with LogicMonitor support it turns out that the updated datasources will not fix the problem for my devices. The initial support rep said these datasources would solve the problem and this blog post makes it seem as though updated datasources are all you need. I think maybe a more detailed write up here would be great letting people know that while LogicMonitor has updated datasources that are capable of resolving the problem the requirement is that your hosts respond to .1.3.6.1.2.1.25.1.1.0. If you update your software to the latest version and still don't get an snmpwalk response from oid .1.3.6.1.2.1.25.1.1.0 then these updated datasources will NOT resolve the 497 day uptime issue. At which point you need to work on an ssh/telnet datasource to check the uptime from the CLI or train your internal team to realize if the uptime was 497 days its likely a false alarm. Maybe having a better alert message containing info about a known issue regarding 497days uptime would also be good. Either way, having this info included here would likely have saved me two weeks of troubleshooting. Hopefully this helps someone else. The devices involved for me were Cisco fabric interconnect switches, UCS-FI-6248UP with the latest 3.2.3i software.
Best Regards.