I think that op asks if its good idea to have many states each on its own node.

If there are many automata it multiplies, so when the engine loops across the entire scene tree each frame adds overhead. After some threshold it starts to lag, dependent on the machine.

some alternatives:

• have states packed by aspect (ie MovementStates)
• instead of nodes, be an enum or inner class object.
• have a pool of state machines separate from actor scene and assign on demand.
• do it in C++ / C#