Sorry for the barrage of replies… It is late. Tomorrow after the kid (PDT afternoon) I intend on taking the camera off of the Pi4 with the screen and putting in on a clone without touch and see what ports 12c-0 is using and also asking the kitchen without camera what i2c-0 ports are in use. I will let you know the results. I wonder if Raspberry Pi thought to make the i2c ports on either addressable???
Sounds like a good plan - No, not really…we have sales contacts but in essence we simply resale their products
They do have a very active forum base https://forums.raspberrypi.com/ that might be better suited for this kind of thing…if you made a post summarizing where you’re at so far, what you’ve tried, etc
The i2c buses are set by their hardware routing (which I believe is the root of the conflict?). Worst case you could also use interrupts or blocking code to cycle when you’d like the bus to doing camera or screen work (I’d presume you’d generally want the cam active at all times and kick the screen on if it receives inputs?)