So from what i gathered, because of the leak you're considering stopping the decomp project altogether. Don't, it's the only way to eventually future-proof porting and developing for this edition of the game. And also the leak doesn't include Switch/Wii U code, and it isn't up-to-date.
Of course, you shouldn't look at the leak yourself as to not risk tainting your work. However, it doesn't mean this project cannot benefit from it in any way whatsoever. RE'ing is not only about the code itself but also about the research process surrounding its reconstruction. If you have another person that isn't directly working on the decompilation look at the leak and describe you, in an abstracted manner, the behavior and effects of a piece of code, it can still work fine in letting you write a clean implementation overall.
Yes, it's harder and you have to be cautious to not accidentally recreate every flaw, but still. As long as you make sure to document well your research around the code, it can work.
So from what i gathered, because of the leak you're considering stopping the decomp project altogether. Don't, it's the only way to eventually future-proof porting and developing for this edition of the game. And also the leak doesn't include Switch/Wii U code, and it isn't up-to-date.
Of course, you shouldn't look at the leak yourself as to not risk tainting your work. However, it doesn't mean this project cannot benefit from it in any way whatsoever. RE'ing is not only about the code itself but also about the research process surrounding its reconstruction. If you have another person that isn't directly working on the decompilation look at the leak and describe you, in an abstracted manner, the behavior and effects of a piece of code, it can still work fine in letting you write a clean implementation overall.
Yes, it's harder and you have to be cautious to not accidentally recreate every flaw, but still. As long as you make sure to document well your research around the code, it can work.