"Terminals" themselves are not the node process that's actually doing the work. The output you see on the terminal you see are merely a representation of the stdin and stdout of the process.
The process itself will be called node and it's functioning is not directly linked to the terminal except that when the terminal is closed ( i.e SIGHUP is sent to the process since it's the child of the terminal ), the process is shut down, since the terminal created the process by forking itself and replacing its contents with your node application. This can be circumvented by adding an & to the end of the command (which makes it ignore SIGHUP) or running your command inside a screen or tmux session (recommended since you can easily connect back)
Hence to answer your questions
Since terminals don't really "contain" your process, there isn't really any isolation between them. If any process has root access, it can mess with any other process
This all depends on the niceness value of the process in question since if more overall CPU time is granted to a process with a lesser nice value, and hence can potentially slow down any other process with a higher nice value if the system is being pushed to the limit
nice allows you to set the 'niceness' of a process, the lower the niceness, the more the priority. As for network you can use trickle to shape the bandwidth
In any case running anything mission critical on a system that's also used for research/dev work is not very optimal and should be avoided whenever it's possible