I mean, you and I have certainly been friendly enough for you to, I dunno, ask me?
In any hardware multieffect, effects take up notably less DSP than amps do—certainly Agoura amps. So the assumption that a ton of effects that fit in Stadium can never fit in Helix/HX makes no sense. As we continue to develop new effects, will we descope them to fit in Helix/HX? Of course not—we don't have to, because they'll likely fit anyway, and given poly-pitch, we're certainly not worried about releasing algorithms that eat up half a SHARC. If we come up with some crazy new extremely DSP-intensive effect that eats up 80% of HX Stomp—will we purposely sit on it because the older SKUs can't accommodate it? Also of course not. There are several instances where POD Go can't pull off an HX amp or effect and we unceremoniously shrug and say "Sorry, guys." It's happening now with Agoura amps and I'm sure there'll be a point where a future effect will also not work in Helix/HX-land, but if I had to guess, it might be due more to lack of capabilities or routing flexibility and less raw DSP horsepower (although that could conceivably be the case as well). For example, Helix/HX has no sidechaining and there are all sorts of cool sidechain-enabled effects out there.
Yes, some effects since around 3.5 or so were created during Stadium work and include tools and things we've learned from said development. We very easily could've sat on them and waited for the June 11th launch, only to drop a 3.9 later in the day with just those effects. But that'd leave a really crappy taste in our mouths, because we never push brand marketing at our long-term customers' expense.
If this is your weird way of getting us to hire you as a DSP engineer...