I can understand your requirement, but i don’t think the pyramid was designed to work in the way… its not modelled around a clip/looper/ableton-like workflow. (e.g. things like patterns were added later) - however the pyramid is pretty flexible … as you say, know it already has patterns, and the sequencer can sequence these patterns.
I think the ‘missing’ element for your workflow is that the sequencer currently stops recording whenever a new sequence is launched - in your context, it seems that you’d prefer that the recording state ‘continues’ ( so it does not have to be ‘reactivated’)
Id guess this behaviour would need to be optional, as others might find the current stop recording as sequences switch useful.
I remember in the past others also mentioning that they’d like similar behaviour (sequencer not stop recording).
as @CreepyPants said previously, contact squarp via the contact form , with details of what you are trying to do , and ideas on how you think it might fit into the pyramid workflow - at the end of the day, they are the only ones that know if this is a major change and if its feasible or not.
Squarp have previously pointed out that the Pyramid firmware is very close to the limits on cpu/memory limitations of the hardware. the firmware has also reached a level of maturity and stability - so most changes are now, tweaks, refinements and of course bug fixes -rather than major changes.