Conflicting element properties. A design issue

As MuseScore is designed right now, it is possible for the user to enter properties for some element types, that are obviously conflicting. See the attached score for examples.
Swing.mscz

There are two D.S jumps with different "continue at" labels, and three System Texts with different Swing settings. Logically these event can not belong at the same positon (tick).

In my view this is a basically flawed design. Instead the instructions for the jump, or changing the swing etc. should be associated with an event, and it should not be allowed to have duplicates of these events at the same position.

It is clear that a change to this design is not something that will happen overnight - if ever - but I can hope that the designers/developers will consider this, and maybe prepare to do a change for version 4.0 :-)

When I raised this with @Mark Sabatella, the response was We can't make guns that automatically prevent shooting yourself in the foot if you are determined to do so.
https://musescore.org/en/node/276617

My response to that is "You should not sell toy guns to children, that can actuallyt fire bullets" :-(