I don't understand this. I worked on the B-2 back in 1987-88, and two things about that program don't add up to having to reverse engineer anything.
First, the B-2 was the first large, complex product in history to be entirely developed digitally. Everything. was in CAD, and only the CAD geometry was authoritative. All drawings printed out were VERY clearly marked warning of this. IIRC, most of this was in Catia, so it should still be possible to read and use that data.
Second, if there's one thing Defense procurement Is good at, it's configuration management. This is doubly true of black programs like the B2, where not only do you want to make sure you never lose data or docs, but also that no bad guys ever have a way to get that data.
Either something went badly off the rails somewhere, or someone needs to rebuild something without the proper clearance. Otherwise, this makes no sense. BTW, the combo of the first complex CAD-only product multiplied by the hideous costs of any black program were largely responsible for the B-2's exorbitant costs.
Congress was stupid to cut B-2 production numbers, though, because the lion's share was fixed, sunk cost that remained the same regardless of whether one or a hundred airplanes were actually built.
(I think I've posted here before about how we spent many millions of dollars to develop a method to repair a major composite part in place. That part was pretty much what you started with when you put the airplane together, so even that was way cheaper than disassembling and reassembling the entire airplane!)