I'm sure this could be done with code or sync robots but I feel it would be more resource heavy or invisible in the workflow diagram.
It would be nice if there were a GO TO function in workflows. GO TO functions have been used in many programming languages to skip to a certain point in the code.
How many times have you had multiple paths all leading to the same result within your workflow, or you have cris-crossing lines all over your workflow just to get back to a point.
A GO TO function would allow you to call a single Same as schematics having a line leading off the page, a bit of a portal to a single point.
One major example we have is with error and rejection workflows. On just one promotion request I have 5 different paths that lead to rejection based on vote, various forms of object validation, or manual termination by the originator. For the most part these all lead to a similar rejection email and exiting the workflow.
Blocks could be used to resolve some of this, but as far as I know blocks are 1 path in, 1 path out and don't necessarily resolve confusing paths. Though if you could use the "GO TO" within a block it could path back to an original workflow point as well.