I do not agree that flushing potentially stale state of not excluded attributes is inevitable and found no clues in the documentation for optimistic lock exclusion regarding this behavior.
The bahvior is even inconsistent as the stale object state is recognized if the version attribute is located in the same table as the optimistic lock excluded attribute.
Additionally, as mentioned in the description, if @DynamicUpdate is used the state of the not excluded attribute may diverge in the database and the entity caches. Without the cache issue this would evite the so called inevitable.

If this really is the intended behavior I would be quite grateful for a hint towards the documentation regarding this.