Aside from the location of the SVM’s root volume, there is no direct relationship between an SVM an a particular node.  The relationship between an SVM and a particular node is determined by what node/port the SVM’s LIF lives on (NAS or SAN) and what node has the aggregate that contains the volume the SVM is serving out.  For example, if an SVM has its root volume on an aggregate in node1 but all its data volumes and LIFs are on node2, then node2 is doing the great majority of work.  Yes, the SVM’s root_volume is on an aggregate on node1, but the processing that takes place on the root_volume is limited to namespace traversal, therefore minimal.  You might even say that in this case the SVM is “tied” to node2, since it’s node2 that’s doing all the heavy lifting.  NetApp SEs, especially during the early days of CDOT adoption, have been known to spread this idea of creating an SVM for each node in the cluster, which is not really correct.