"Getting even weirder, checked again few minutes ago on the same machine and it now shows correctly 22622. Must be another A/B testing B.S"
Perhaps CMD is updated in some background process when main installation is completed?
Possible.
But I had rebooted already more than once after the update and when I submitted the FBH report earlier I did it with recording, so that they can see that I had 22621 in CMD prompt and 22622 in Winver.exe and system info.
Go figure?