I suspect this model is intended to describe the original MVC pattern of event-driven desktop GUI apps rather than MVC as commonly implemented in server-side web frameworks. The view in particular in this diagram doesn't quite map to what web2py calls a view.
Note, some frameworks, such as Django and Flask, use different terminology for the controller and view. What web2py calls controllers, Django calls views, as they are functions/classes responsible for updating the model data or getting data from the model to be displayed to the user. What web2py calls views, Django simply calls templates. Django considers the framework itself (in particular, the logic that routes HTTP requests to views) as the "controller" part of the MVC architecture. For further explanation, see
here and
here.
The point is, there can be a lot of confusion about terminology. So, rather than ask whether web2py allows the "model" to be updated from the "view", it might be more productive if you explain exactly what you are trying to achieve (and why).
Anthony