My guess is the shm to detect multiple copies linked in would probably be a lot of complexity for the sole purpose of trying to compensate for a really bad practice.
Usually none of these issues are dealt with in the shared memory sdk you’ll be using, so you gotta model it with mental experiments just like you would a lock free implementation in a threaded process.
Simple no, doable yea, error prone you betcha.