Thank you for your quick answer.
 

I appreciate the suggestion to use IP&MAC binding as a workaround for devices beyond the 32-entry limit in Address Reservation. However, it seems IP&MAC binding primarily serves as a security measure to prevent ARP spoofing by associating an IP address with a specific MAC address, rather than actively assigning or reserving IPs via DHCP. It doesn't change the IP on the client device itself or handle the assignment like DHCP reservations do.

To make it work for fixed IPs, I'd still need to manually configure static IPs directly on the additional devices (outside the DHCP pool to avoid conflicts), but that's not feasible for many of my IoT devices, as some don't support static IP configuration and in general it's not practical to access and change settings on each one.
 

My setup relies on fixed IPs for integration with Home Assistant, and right now I need at around 40 DHCP reservations to cover my current devices, so 64 possible DHCP reservations or 128 for future-proofing would be great. Ideally, the limit could be removed entirely (I don't know if that would be possible or if there is a hardware limitation), since other users with larger smart home or small business networks might require even more.

I’ve noticed some TP-Link models, like the Archer C1200 (64 entries) and TL-ER5120 (1024 entries), support higher limits), despite being cheaper or similarly priced to the Archer NX200. I’d prefer not to add more devices just to manage DHCP reservations.
Could the development team consider a firmware update to increase or eliminate the limit on the Archer NX200?
 

If there's another way to achieve more than 32 true DHCP reservations without requiring static configs on the devices, please let me know.

Thanks for your help!