An SPA architecture is very simple and it does a great job of implementing a strong degree of separation of concerns and maintainability. Essentially, a proper SPA architecture looks like: one backend server that exposes a CRUD REST API (that could call lambda functions here and there when you need to do complex calculations), and then you have your SPA which is hosted on a static file storage service and it's literally just a bundle of html, css, and JS files.
Example architecture: EC2 (Backend) <-> S3 (Frontend) <-> Cloudfront
It's that simple. Our backend is a feature complete version of our application that we can interface using HTTP methods, which is incredibly powerful because it means we can have multiple clients (native, mobile, web) that all interface the backend instead of coupling the view to the server as we would do using what you suggest in your article.
And building an SPA that interfaces a REST API doesn't mean reinventing the wheel. You and other developers who are too stubborn to look past their MVC bubble are just ignorant of the massive amounts of progress over the last ~5 years that the web development community has made in enabling SPA best practices.
Just look at Vue-Cli or Create React App. They're incredibly well documented resources and it's incredibly easy to onboard an engineering team onto a SPA project because of how developed the front-end ecosystem is. Everything you would ever want to do has been done before and theres an infinite number of resources to consult when trying to decide what's best practice. The web development community is bar-none the biggest open source community right now and it shows. I've on boarded teams of developers to using SPAs and when they come from a background of MVC they tend to fall in love with the idea of components and encapsulation and philosophies of React and they become agile like you would not believe.
Also it's funny you praise the model-2 variant MVC pattern. I just moved a team away from an architecture like that to a SPA one and the difference in productivity from the team was night and day. That architecture was fucking disgusting monstrosity and it should stay in 2008.