I can personally second what Spike has said about the game being very crash heavy, that said, from what the author has said and looking at the input file it appears the movie was simply made by playing the game in real time (well, as real time as libTAS will allow anyway) and as such is quite subopitmal. I understand dealing with a crash prone (and allegedly desync prone though I haven't played around with it enough to confirm myself) game is really frustrating but it seems to me that Tegron doesn't quite understand the TASing process.
Luckily there are guides that go over just that, which I personally would recommend reading or watching the ones on youtube. Of course they don't apply to the libTAS workflow exactly, but they should still give a good idea of how the process should look like.
As for the goal choice, I understand starting out with the shortest possible ending, though I hope to see a more "full" run if the TASing conditions can be improved.
Voting No for poor optimization, but would love to see you have another go at it!
