Take Electron,
I'd rather not, thanks. Unless you meant in the sense of "take it out back and shoot it", in which case we're bloody trying already, it's not that easy.
I have a hunch that FORM is not made up of easy to grok software designs or it would probably be true that other folks would have contributed in a bigger way regardless of academic stimuli. If that is indeed the case, as is common in research-academia software product, then tie a bow on it and send it off to the Smithsonian.
I would be really quite surprised if some enterprising 19 year old whiz-bang genius from Iceland didn't re-write it in Mathematica.
Still would be a net loss for science, as a critical piece of software infrastructure would become tied to Wolfram's proprietary black box. Also I think academic software benefits less often from a random precocious outsider fixing things, because in addition to good programming knowledge, it requires a fair amount of subject matter expertise, what is rare to be found both in the same person.
A bug in the code would throw doubt on every paper published with it so the expected value for any individual rewriting it or making any modifications is extremely negative for their career.
Sure, but how long will that take and how robust will the result be? Given the description of the design, it basically sounds like it does efficient block-level storage management in order to handle the petabytes of data that it might need to churn through, so basically you're reimplementing a DB storage engine, which is no small feat to get right and performant.
Furthermore, is there a test suite to validate that the FORM2.0 yields the same results for all past papers?
These problems are not unsolvable but they're not trivial either.
This seems very pessimistic view. FORM was written by mortal humans (with much cruder tools!) in the first place, there is no reason to believe it couldn't be done again if need be and even improved in the process; its not some irreplaceable artifact descended from heavens.
On the other hand, I imagine it would take bit more than just maintenance to make the 30 year old C codebase welcoming for new physicists to work on.