Hi again Tim!
> current Cylc parameter combinations results in a Cartesian product of satellites and sensors, ...
Yes, foo<m,n> is equivalent to a nested loop over m and n - because built-in task parameters are intended as a clean replacement for messy Jinja2 loops. Given that your use case is more complex than that, then yes, you would have to revert to Jinja2 templating, or a combination or Jinja2 and parameters.
I'm inclined to think there are diminishing returns (relative to effort) from trying to replace increasingly niche uses of Jinja2 with built-in functionality. But if you can give us a concrete example of what you want, we might consider it. Otherwise, stick with Jinja2 (or EmPy) - or wait for the future suite configuration Python API!
Hilary