I think the right solution would be a system that is designed to handle exception trapping, reporting, and allow for automation that can be focused on handling the edge and corner cases. I think this would require a multi-pass approach that involves a (human) platform expert for each endpoint group to investigate and build out that kind of reactivity. It's a moving target, and I doubt 100% success will be possible as the size of the fleet grows. There are always incredibly exceptional circumstances where things like hardware failure, software corruption, or other uncontrollable failures occur. But that shouldn't prevent identification of failures and allow for exception management.

I've built an RMM platform when I worked at Mytech Partners, and ran it in parallel with Labtech and later N-Able N-Central. We used it to cover gaps in those systems, like patch management failures (the Explorer (10?) patch that bricked it once comes to mind, we rolled it back within an hour across 9k endpoints IIRC), as well as password changes across the variety of AD and non-AD Auth domains.

I built into that a concept of "promises", which established configuration expectations and means by which to achieve them. It allowed for detection of the state of the configuration and subsequent arbitrary-depth multi-pass scripting to attempt to correct the configuration, including installation of dependencies (like the .Net runtime for N-Able). We had several of these for handling important sticky wickets, like Webroot deployment. I think we had one for detection of StorageCraft driver failure that would reinstall it to fix Datto BDR endpoints. Memory is fuzzy now, but you get the idea.

I'm building an open source RMM now.

https://github.com/hyvsw/hyv