Unfortunately, the satellites cannot be programmed with any different WiFi settings than the router. I believe what you are experiencing is a race condition. Any time that the Orbi system is rebooted, the router will have its WiFi signal enabled before the satellites do for any WiFi client. In your case, the Ring doorbell sees the 2.4GHz signal from the router before the closer satellite has its WiFi enabled, so it will bind to the router. IoT devices are not expected to roam like a smart phone, laptop or tablet, so an IoT device will not look for a better signal once it already has one.
You may be able to lower the power level of the 2.4GHz signal so that it is too weak for the video doorbell to use, then it should bind to the satellite instead as long as the satellite signal is also strong enough. You can experiment with this and see.
I have a similar situation with a smart garage door opener and a WiFi security camera in my garage that are close to a satellite, but far from the router. Anytime the router reboots, satellites also reboot, so the IoT devices bind to the weaker WiFi from the router instead of to the closer signal from the satellite. The only workaround I have to "correct" this is to then power-cycle reboot the camera and smart garage door opener, then they bind to the closer satellite. I reported this issue to NG while I still had support, and there is no means of them fixing this issue. I would bet that other mesh router systems from other vendors would also have this same design flaw.
