Machinbird
In dealing with the product limitation of current Pitotīs, Diversity could be implemented (for "brief" AS fluctuactions) and probably could be better than the use of a "memory mode" band aid. In this aspect Turbine D approach could be one method.
Pattern recognition techniques are powerful in preventing and after the (possible and improbable) UAS events.
This can be done and the on board redundant processing power allow the implementation. The required R&D could optimize defining the extra required hardware.
Ideally diversity could perhaps help in some (extreme) cases (Birgenair and perhaps even Guam B2) providing less precise data but avoiding abrupt a/c config changes.
Diversity (inside the Redundancy concept) should be applied to reduce surprising and dangerous abrupt transitions from "Normal Law" to "Murphy Law scenarios"
with unpredictable consequences. All this for creating degraded, but administrable situations. Obviously always we will face limitations. There are some possible but improbable issues that could be considered in the System (a/c+operation) R&D without incurring in initial prohibitive costs. The 737 rudder (PCU) issue is an example of this "costs" (without mention the lost lives in FLTīs 585, 201 and 427). Competent designers in good R&D teams know well this matter.
Drifting a little bit:
L1011-500 superb characteristics may be could be mentioned in this aspect. The challenges they faced were very "high" And they also put an angel to fly (high
} at FL600 in 80 days