No, I don't have a link. I just played with a reasonably big table. As a starting point I had this output from sp_spaceused.
name rows reserved data index_size unused
Orders 1032105 301952 KB 199632 KB 101792 KB 528 KB
ALTER DATABASE Northgale SET ALLOW_SNAPSHOT_ISOLATION ON
Then I did:
SET Freight *= 1.2
The table now grew to over 500 MB. I also ran:
SELECT * FROM sys.dm_db_index_physical_stats(db_id(), object_id('Orders'), 1, NULL, 'DETAILED')
Which showed that there were a million in version row count. (Note, you need SQL 2019 for to have sys.dm_db_index_physical_stats to give you information about version records.)
Then I ran
ALTER INDEX PK_Orders ON Orders REBUILD
And sp_spaceused now reported the original size, and sys.dm_db_index_physical_stats reported no version records.
With REORGANIZE that did not happen.
I was quite surprised, because I had been taken for granted all these years that once these 14-byte pointers had been added they would remain as long as the database had some form of versioning enabled. But in a way it makes sense. If you take a big table like an Order table, most of the rows just sits there, and the 14-byte pointers would only eat disk space.