An automatic guidance system in a fixed-wing aircraft is given a route with waypoints, and autonomously navigates between them. It needs to know things about horizons, Great Circles, collision-avoiding altitude change plans, least-time routing, reachability of nearby airports given available fuel weight, etc. There's no real way to implement this with anything less than a CPU with a full (realtime) OS and a software stack on it, full of complex pre-baked databases, with multiple inter-related components from different vendors in the mix. It's frail. Of course it needs a backup.
The kind of system I'm talking about here, on the other hand, is essentially a physical model of the three available controls and how they interact to move the aircraft (and thus predict how the aircraft will be moved); combined with actuator-sensors, accelerometers, and gyroscopes to read off how the aircraft is being affected by those controls (and thus correct the prediction)—enabling you to translate linear movement of a flight-stick to linear movement of the helicopter. It's a dynamic torque model feeding a control system, with a user-supplied reference point. You can make an ASIC that does that and put it through fuzz-testing for literally every potential input combination it'll ever receive.
Yes, said ASIC might physically fail (even after you've done an extensive burn-in test)—but, given the tolerances we have in making ruggedized solid-state electronics these days, vs. the tolerances we have in making mechanical systems, it'd be the least likely part in the control chain to fail.