May I suggest that all the discussion about temperatures, pressures, speeds, vibrations, etc become totally irrelevant within mili-seconds of the disk rupture.
Mostly agreed.
Would you also agree that it is those data
up to the pont of failure that are of great interest in getting to root cause, as well as a possible means of using existing sensors to identify a performance change that allows the pilots to
throttle back,
or
secure
an engine changing from steady state into "troubled state" before it gets to "it just failed, oops there goes the turbine wheel" state?
From previous discussion, with different cueing,
perhaps the "time for 30 seconds" protocol for engine performing in X state will in some cases change to "retard to idle" or "secure"
if the proper cueing can be figured out from sensors. Being able to adapt the checklists (and the ECAMS available) for the malfunction before it becomes an emergency or materiel failure allows the company to save an engine (to be repaired upon landing), rather than sending bits of itself through the airframe. It's also both safer, and more comforting, for the paying passengers.
It is possible that current sensors can't do that, or provide the granularity required.