If I understood what you mean, it doesn't sound like it works in any practical sense, because Red Hat wouldn't take you as a customer for release n + 1.
1. You purchase release N
2. You distribute the source code to release N.
3. Red Hat terminates you.
4. You needed Red Hat N. You're doing enterprisey things or using software that runs on Red Hat.
5. Red Hat releases N + 1.
6. You try to get release N + 1 from Red Hat, because you're in the ecosystem, doing enterprisey things, using software that runs on Red Hat
7. Red Hat remembers what you did on release N and doesn't offer you release N + 1.
It doesn't quite seem like the purchase model. This barely seems to get you anything over what a Rocky or Alma or whatever scrape to put together with Red Hat damming distribution, so you might as well resort to them right at release N instead of paying Red Hat for it.
1. You purchase release N
2. You distribute the source code to release N.
3. Red Hat terminates you.
4. You needed Red Hat N. You're doing enterprisey things or using software that runs on Red Hat.
5. Red Hat releases N + 1.
6. You try to get release N + 1 from Red Hat, because you're in the ecosystem, doing enterprisey things, using software that runs on Red Hat
7. Red Hat remembers what you did on release N and doesn't offer you release N + 1.
It doesn't quite seem like the purchase model. This barely seems to get you anything over what a Rocky or Alma or whatever scrape to put together with Red Hat damming distribution, so you might as well resort to them right at release N instead of paying Red Hat for it.