PreSonus, PLEASE PLEASE PLEASE ignore your users here. Apple, McDonald's, Google... they all understand that users aren't designers. Clay Christensen taught them this with the Milk Shake paradigm. It's about the "job to do".
StaffPad proves that Dorico's complex articulation mapping features are like Notion's rules... composers complain about Dorico constantly for the same reason Notion gets flack. StaffPad doesn't force users to map ****. Users don't need more ways to configure. We need to use. The fewer barriers to that goal, the closer you are to getting it right. Even Infinite Brass, despite not sounding 100% real to most people, has led many to leaving Spitfire because the library doesn't even use key switches. The instrument is smart enough that it doesn't need to. The best paradigm is that, whichever way you go... you aren't putting setup complexity on users.
Studio One's maps are good enough that any Spitfire or Orchestral Tools (the two most popular high-end libraries) can be mapped adequately in S1. That's good enough to wait until the industry matures. A composer's "job" is NEVER to configure. It's to open up Studio One and start writing music. Please don't complicate the program's front end, rules, XML, etc. Make the engine smart enough that we never need to think about that.
1) Studio One already has an in-app sample store. Why not partner with companies the way StaffPad did?
2) Studio One could implement the VST3 ability to auto-map samples. No editor windows. No dialogs. Just open S1 and write music.
3) If I still haven't convinced you, please realize that Cubase got this horribly wrong. Google how many complaints, for over a decade, are online about expression mapping taking enormous amounts of time, once? NO, every time someone buys a new library.
P.S. I have no stake in this. I write in StaffPad, master in Studio One. But having spent years in this mess, and finding relief in a different app... I am never looking back to the DAW to write music, just master it. Why? Because an app that had the "just open it and write" paradigm was good enough that I didn't want to look back. If Studio One gets this right, really right, then maybe I'd have a reason to write in S1 again.