View definitions do not keep track of a timestamp when they were last changed and do not have any point-in-time or snapshotting support.

When using views inside of multi-document transactions the view definition at latest is always used even if its definition is different at the timestamp for the transaction snapshot.

Note that this is just an issue for the view definition and its aggregation pipeline, when it is resolved and we are reading data from the underlying collection snapshot isolation work as expected