No, this is a standard behavior.
There is no general mechanism for caching. It is done case by case in some Model. But very few of them as cache, it is done only with mainly static data like views.
The mechanism is documented in Cache — Tryton server
I do not think so.
proteus is not really the right tool for that. You may have a look at Flask Tryton Module but you will need to upgrade to a supported version.
But the main question is why and how a call to model.sale.sale.read trigger a cache invalidation of the views. Such invalidation can only happen if one of the Models are changed: ir.action.*, ir.model*, ir.ui.view or ir.translation. But read call are read only by default.