Personally, I think they jumped the shark with the release of this ISO
I found this lame explanation yesterday
To offer a clarification on these releases – 19H1 and 19H2 share the same servicing content. That means they share the same Cumulative Update package. For the small subset of Windows Insiders (the 10%) in Release Preview who were given the option to install 19H2, an enablement package is downloaded from Windows Update that turns on the 19H2 features. This *changes* the build number for the OS from 19H1 Build 18362 to 19H2 Build 18363. Because they use the same servicing content, the build revision number (the number that comes after the dot) will always match between 19H1 and 19H2. As we continue to test our servicing packages in the Release Preview ring, Insiders on 19H1 and 19H2 will get a single Cumulative Update with the same fixes.
Which they later updated to this
We have increased the “seeker” experience for 19H2 in the Release Preview ring to 100%. This means that everyone in the Release Preview ring should see a Windows 10, version 1909 update available If they go to Settings > Update & Security > Windows Update. Insiders who choose to install this update will be updated to 19H2 Build 18363.329. We are also beginning to push 19H2 out to 10% of Windows Insiders in the Release Preview ring as well. This means 10% of Insiders in the Release Preview should see 19H2 Build 18363.329 offered automatically.
NOTE: IF your PC uses Windows Defender Application Guard (WDAG) or containers, you will not be offered this build of 19H2.
I can confirm that my Insider machine on the Release Preview Ring, is not being offered the 19H2 build
EVEN though it does not have WDAG nor containers installed.
IT is currently running the same build that is currently publicly available to everyone 18362.329