I think some devices are much more focused on certain ‘musical genre’ workflows…
e.g. a drum machine will have a certain view focus on how percussion works, and so have mutes in a particular way.
(so not surprising, you mention roland/electron in this regard)
whereas some sequencers are more general… so have (and imho, should have) a more more generalised workflow
e.g. hapax’s drum tracks are pretty much a ‘skin’ over a normal polyphonic track, where notes = percussive track.
this gives 90% of what’s needed to 90% of users…
but generalisation does mean some small compromises, you’re not going to implement a very specific workflow, that inconsistent with other workflows. and also might be usable to a (relatively small) % of users, given you have a broader user base.
(more generalised instruments, will have users using in a wider set of genres, almost by definition)
so the question is (for developers) how do you support these use-cases…
many users say ‘just make it an option’…
however, generally developers do NOT like this approach, for a variety of technical reasons - basically, it will bite you on the a*se later
( this is a common, ‘conflict of interest’ for devs vs users - users see it as a quick/easy thing to do, but for devs… ‘its not that simple’ )
instead, the better approach is to find a more general approach, is consistent and has multiple uses. but this is much harder to design, and also implement = more dev effort.
this was why I mentioned snapshots… they might not quite do what you want…
but they are a powerful concept, that could potentially with a small tweak, do what you need - but also have a much wider range of uses.
e.g. not just muting, but for example, resetting fx parameters between song sections.
its also not a new concept, but rather an extension to something already preset.