Option to pin node placement relative to Merge Node

For an end user it is not clear what logic drives the order in which nodes are connected to Merge Node when working outside of the Node Graph view. With more complicated node trees I found myself checking if the Transform node is the last one for example as some actions in the viewport put other nodes after it.
Maybe this area could use some clarification in the docs?
A band-aid solution I'd be fine with is to pin nodes to Merge Node so no other node can be placed between them:

Start by comparing node connection order in the Node Graph view with the behavior of the Merge Node, Transform node, and viewport actions described in the issue. Determine whether the intended outcome is documentation clarifying the ordering logic or an option to pin nodes, then define completion around one of those outcomes and verify it with a more complicated node tree.

Written by the indexing model from the issue text.