Not sure what you are trying to accomplish.
A node is place where edges meet. It cannot distinguish between the edges to do something different based on some attribute of that edge.
>(e.g. the node just representing a junction which is used by different type of modes; the nodes along a similar path which is used by mixed traffic but each node does not act as a transfer point)?
You are talking about some solver behavior on how it should deal with that node. Are you writing a custom solver? In that case you can manage the connectivity and decide what do when you arrive at that node.
There are various ways in a network dataset in how the connectivity at edge end points can be handled. One is with from/to elevation values on the edges, another is to use true 3D geometry of the edges, another is to use any vertex connectivity and yet another is to use sub-types. But in the end once a junction has some edges connected to it, the only way to restrict movement between a set of them is to add a turn restriction.
Jay Sandhu