Is MAX(rowversion) optimized for the table?
No, it doesn't appear there is any special treatment for rowversion columns.  This small demo confirms the entire index is scanned to find the MAX value:
CREATE TABLE dbo.RvTest
(
    Id int NOT NULL,
    rv rowversion,

    CONSTRAINT PK_RvTest PRIMARY KEY (Id)
);
GO

INSERT INTO dbo.RvTest
    (Id)
SELECT DISTINCT 
    [number]
FROM master.dbo.spt_values v1
WHERE 
    v1.[number] IS NOT NULL;
GO

SELECT MAX(rv) FROM dbo.RvTest;


Interactive db&lt;&gt;fiddle link
This makes sense when you consider that the rowversion is unique across the whole database, rather than a specific table:

Each database has a counter that is incremented for each insert or update operation that is performed on a table that contains a rowversion column within the database. This counter is the database rowversion.

It doesn't look like SQL Server stores table-specific metadata about rowversions.
If you need that check to be very fast, there's nothing stopping you from indexing that column yourself:
CREATE NONCLUSTERED INDEX IX_rv ON dbo.RvTest (rv DESC);

Which results in a single row being read for that MAX query:


As a side note, as Panagiotis Kanavos has mentioned in the comments, this is usually used for optimistic concurrency checks - to tell if a specific row has changed since the last time it was read.  The way you're using it is still valid (keeping the last maximum, and checking the current max to see if any data in the table has changed), although the built-in Change Tracking feature might be attractive to you as an alternative.