Root cause analysis isn't the only reason: it would be good for pilots to have this case study, as well as analysis on how systems responded to the abrupt change.
Having this data is strictly better than not having it.
Yep, could be used as a "this is exactly what you do in this scenario" example for future pilots, or a "what did they do wrong" type real-world exercise for pilots to review (with no blame given to the OG pilots in this scenario for example).
There could be steps that weren't followed, there could have been training gaps. There could have been secondary impacts of sudden depressurization that could have spiraled out of control, but the pilots thought on their feet to save the plane. We'd want to know exactly what they did so we could add it to the recovery process.
Theory: having less privacy makes things easier for accident investigators, post-mortem.
Reality: In this case, the pilots did their job and got the plane down safely despite rapid depressurization and literally having their headsets sucked off of their heads. It is extremely unlikely to be pilot-error that a door-plug ripped off the airframe at 16,000' or that investigators would learn anything significant from the process in the flight-deck before or after the incident. At least nothing that would root-cause this incident.