Oh for goodness sake - when will you realise that the above scenario is a non-event and has probably occured thousands of times, due to a myriad of different causes, and has probably never caused an accident before, due to pilots monitoring their goddam thrust settings! We've all experienced A/P and A/T misbehaviour and drop-outs and its our job to manage them.
Well this time it did lead to an accident and I fear this sort of explanation in the light of public awareness of what triggered the accident would not go down well with certain groups, say your passengers for instance. Yes the crew would appear to have been incompetent, but having exposed a new hole in the cheese to the scrutiny of investigators and the traveling public alike, it will be incumbent on the powers that be to institute a technical fix in addition to any remedial training requirements both specific to TLH and any more general requirements they may come up with. That's just the way the world works.
In other words incidents like a malfunctioning RA#1 that trips the A/T into an un-commanded mode at an inopportune moment is a benign failure that doesn't concern anyone outside the industry, until such time as it is linked with an accident like this one. Then it's no longer benign.