I agree with FURRYe38 . The nature of the Guest WiFi network has changed over the years. My understanding is that there are two fundamental reasons to have a Guest network:

To have a network that is "walled off" from the primary network. Devices on the Guest network cannot reach the primary network.
To have a network that is easy to share without compromising the password of the primary network. Often the Guest network password is simple to enter and since none of the primary devices are using it, the Guest network password can be changed at any time without disturbing the primary network. (The thought of reconfiguring dozens of WiFi devices with a new password can be overwhelming.)

The original Orbi product (2016) had it both ways. The network could be configured to keep devices on the Guest network separate or to allow them to interact with the primary network. I thought this was an ideal solution. Suppose family or friends come over and one of them says, "Can I print something out?" No problem. Just switch the option to "Enable" and tell them how to access the printer. When they leave, disable the connection (or change the Guest password). No impact on the primary network at all.

Unfortunately (in my opinion) the folks at Netgear went "all in" on the first concept: keep devices off the primary network.

Whereas the original Orbi had only one IP LAN Subnet, the AX product line places the Guest network in a separate IP subnet that cannot interact with the primary network.

If you want Guest devices to be separate from the primary network, then the Orbi assigning them IPs in a separate network should be "no problem". These are "Guest" deivices. They come and go. Who cares what IP address they have for the brief time they are on the network?

Outdoor Wifi Satellite RBR750