I know this won't happen: it would take too much reworking of the code to secure one area, while opening another. The code as it stands is an all or nothing proposition. You can change legally what you can change, but any reverse engineering not covered by the EULA voids any future support (to say the least).
Lastly, the origins of the new sound files' source may not be verifiable, which would open the developer (if they were to go for this,) to potential future punitive legal actions by the original owners of those sounds.
Welcome to the high stakes world of intellectual property law
