i) Re-writes are rarely the answer and if you must do them targeted re-writes are better than whole app. New code tends to mean new bugs. It's often a case of the devil you know vs. the devil you don't.
Please, go to the authors of Wayland and stop them while you're still in time!!!
X can be patched! we dont need wayland!!!!
Well I guess you don't win any reading awards.
ii) It seems to imply that you couldn't just do a parallel development. MG definitely has money and they are hiring. No reason why you couldn't put the current code on maintenance and move your best talent to make the new branch.
the fact is that the website is not safe TODAY not tommorrow.
If it will take a month to rewrite the code from scratch, do all end-to-end testing and it is considered infeasible to take the site down. Then the site will be up whether they are re-writing the code or not. So you might as well write the new code. Clearly your experience with SDLC is a little thin.
These two assumptions make me wonder if you've every really been involved in large-scale development work.
I think this point stands mousey!