The solution I found is to separate the relevant releases by component. For example, to have noble-updates-main, noble-updates-restricted, noble-updates-universe, noble-updates-multiverse. With a single content-view for all, it seems to work.
Well, in our case we have the problems with the EL-Repositories (BaseOS, Appstream, etc.).
This would mean to change part of our configuration, with a lot of backlash from Change-Advisory-Board and so on.
Besides of that, the limitation of 16Bit (2^16=65536) should not exist in the first place nowadays.
I know that in 1990 this was a big deal, because HDD and RAM had very limited space,
but since earliest 2004 a 32Bit value does not make a dent into the systems the various engineers created.