I approach this by writing exploratory prototypes with good modular boundaries, but stub/hacky implementations. Keeping it simple lets me throw modules away as I refactor, until everything's been rewritten and then I ship it.

Sure, and that works great for a personal approach to code. But when your lifecycle from requirements through release needs to be validated, something more scalable is required. Sometimes that scalable thing is "anyone shipping prototype code will be fired."