That wouldn't solve the problem; that would just make the scenes take forever.
Think about it this way: Scene duration is equal to the number of frames divided by the frame rate; mathematically:
d = (x frames) / (y frames/sec)
The original game specified a number for x, but not for y (citation needed; I haven't actually checked this); y was determined by how fast your computer could draw frames. The KS version, for whatever reason, specifies a very high y. In order to keep d at a reasonable value, the KS devs dramatically increased x. With a higher x and higher y, d remains essentially the same. Unfortunately, this interacts poorly with how the cut scenes are scripted. The cockpit, for instance, shifts forward every few frames; more frames means more shifts, which eventually shifts the entire sprite into view.
If I just change y (which doesn't even require a fake audio file; I can just change the hard-coded number), without also changing x, then d will skyrocket and animations will seem to take forever. Further, without changing x, the ghost cockpits problem remains; it just takes longer to happen. Changing y is a code change; I can do that easily. Changing x is a data change, and there are bound to be lots and lots of x's out there.
