Yes. The Max patch has scripts that create associations only with the track it’s loaded on. Each device is independent and you can use as many as you like.
This seems like there is probably some outside source causing the issue.
The conversion from clip name to program change is relatively simple. The name is filtered and matched to a list in a database. The corresponding program change is transmitted when the name is matched.
To rule out outside problems you can simplify down to just the Octatrack and pattern clips in a new project.
Try switching back forth between two empty patterns on the Octatrack and see if the problem persists.
It’s possible you are sending program changes in a loop through the Octatrack. Check to see if you have the MIDI out of the Octatrack (or another device) connected to the computer and try disabling MIDI inputs to the computer.
The last thought is to try another MIDI interface and/or cable if available. Some cheaper MIDI interfaces can’t handle program changes, sysex, and cc messages well.