In my experience with solution architectures, when talking to execs, it is more efficient to create ad hoc visio diagrams than trying to tweak ArchiMate models to be intuitive for execs. Talking with execs doesn’t happen every day, so having bespoke communication is not a problem.
Breaking the model by going a sort of ArchiMate-in-name-only route is the worst of both worlds. It damages your model (what if you ever want to move from one tool to another?). It also ‘dumb-down’ your modelling tot what doesn’t confuse the average exec.
For me, ArchiMate is a language for Architects. And a good model can be used for all kinds of analysis and reporting (such as in reporting for regulators). During this week’s EAC Europe 2020, a colleague of mine reported on APG AM’s Process Model that is done in ArchiMate (advantages and drawbacks with regard to BPMN) in a single model with the architecture model as well (>100,000 elements and relations, might at this time even be around 150,000). The result is a very functional model where you can link risks, controls, etc. etc..
And if Abacus allows you to create any relation between elements, it is in my view not ArchiMate compliant (neither is Sparx btw). It is a model, so in that sense it is better than Visio alone (but there is a solution that use Visio, but has ArchiMate as a model in the background, iServer from Orbus so that might enable you to use ArchiMate and non-ArchiMate more integrated — I don’t know haven’t worked with it). Abacus, as I recall, also is non-compliant in that it is not possible for a single element to be part of two different nested Aggregations (as Abacus uses nesting for additional model structure in the tool).