The underlying motto of what I have written is to keep things simple and I feel that, one way of doing this is to keep the model node away from the view. I tried it in my recent work and found it useful and worth sharing.
According to the above mapping model the View contains the screen layout which forms the presentation logic. It should contain the value nodes and value attributes which would assist in the creation of the presentation. Try to avoid mapping the model nodes into the view.Instead map the model nodes and the value node into the controller and write methods which would help in copying the values from the model node to the value nodes and vice versa.
Now suppose there is any structural change in the backend and the deletion of the model becomes a necessity. Then you can go ahead delete the model and then create it again. As the RFC do not have any mapping with any other components other than the component controller you need to bother only about change in the method which copies the values to the corresponding nodes. Thereby reducing many overheads you might have to come across.
This method of developing WebDynpro application was helpful in creating small components (one view and RFC as backend) and change in the model would mean only that a change in the component controller is required. This was not however tested in big applications containing numerous screens which would load the component controller heavily. Also the methodology in the light of dynamic programming is also to be tested for.