Normally a GUI can be either simple to use or cover all the possibilities of the system it is used to control, never both. Most are far too complex and still don't cover all possibilities. Mikrotik's one covers all possibilities and is appropriately complex.
What might be interesting would be some kind of an external application converting drawings similar to ones you've suggested into configuration commands. But that simple drawing where ether1 and ether2 are member ports of a bridge named bridge already lacks the possibility to choose whether the bridge should make use of the "hardware acceleration" or not, as well as to set all the other options related to the bridge and to its member ports. And as soon as the user has to set a couple of checkboxes, a couple of drop-down menus, and fill in some free text fields, he quickly becomes as lost as with the regular GUI available in Winbox and/or WebFig. So you'd have to define the parameters of the environment which never change in your application scenarios and make them be set that way automatically, with no possibility to change any of them. Default settings of the values are no option, people who don't know exactly what they're doing tend to start clicking various settings if things don't go the way they expect them to, in hope that it will fix the problem, but actually causing even more mess.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.