Idea to improve Sql server query performance with timestamp column

A timestamp column is an automatically increased value (db) globally unique binary value, on every row update, maintained by the SQL Server engine.
Since the timestamp column can be indexed it could potentially allow much faster querying for queries of the type "give me changed rows since last check", by adding a where condition in tsql pseudocode style `WHERE row.timestamp.ToBinary() > @LASTCHECKED`
Is it worth investigating with performance testing of some large datasets ?

The issue names no files, tests, or entry points. Begin with performance testing on large datasets using SQL Server queries for changed rows, and determine whether an indexed timestamp column provides a meaningful improvement over the current approach.

Written by the indexing model from the issue text.