The Gaia OS should try to seek out an idle CPU first, and once the script starts it won't be allowed to completely monopolize a single CPU, but will be given much higher scheduling priority (i.e. more CPU slices). Even with elevated priority the script can be shuffled around to different CPUs that are idle, so impact against fwk processes should be minimal.
So once again the only caveat is to ensure at the start of the script that there already isn't another copy of it running and you should be OK. Typical daemons do this by writing their Process ID (PID) into a known file in someplace like /tmp when they start up, and when the script starts it checks for the presence of the PID file, and if it exists, see if the stated PID value is associated with an existing process. If so the script terminates immediately.
When the script successfully finishes execution, the PID file is removed. Even if it somehow crashes/aborts without removing the PID file, this technique works to keep multiple instances from running.
Gaia 4.18 (R82) Immersion Tips, Tricks, & Best Practices
Self-Guided Video Series Coming Soon