The MVC model is intended for the construction of interfaces ( link ) and not all application architecture. Other models may also arrive at the same result and the arguments you put forward will not necessarily be reached by just making use of this template.
Business rules and persistence issues are not covered by MVC, since their primary purpose is to construct user interaction objects that allow the use of unit tests during their implementation.
It is considered a mistake to implement business rules in a controller as much as it would be wrong to implement them in a form and for the same reasons.
The implementation of business rules can be located in several parts of the application depending on the architectural model chosen. For example, if you are going to use Domain-Driven Design (DDD) then business rules will be implemented in domain classes and service classes, whereas persistence will be managed by repositories, whether or not they use a persistence system automatic.
There is a product at link