Now that REVISIONTIMESTAMP uses a different flag in master, the only thing left to cause vary-revision is self-transclusion (core or via Lua). Once that change goes out, any remaining use should be investigated if it is still problematic. It might be useful to add a vary-revision-hash option to handle race conditions where a page gets auto-merged and thus the self-transclusion is different than the text proposed in the save operation. Normally, I don't see why a reparse would be needed.
Customize query in gerrit
|mediawiki/extensions/Scribunto||master||+8 -3||Use "vary-revision-sha1" over "vary-revision" in getContentInternal()|