Yep, but there are other things that seem to me "off" in your configuration.
The DHCP client (where needed[1]) should be running on the bridge1, not on the wlan1.
Since wlan1 is (correctly) part of the bridge, it doesn't really exist anymore externally.
And the DHCP relay should not be needed at all, your setup corresponds - in theory - to a "dumb" switch of which one of the ports happens top be a wireless link, since the pseudo-bridge being not a "proper bridge", it may actually need it, but I wouldn't be so sure.
As well proxy-arp - if actually needed - should be only on the outside of the box (the bridge) contining the various interfaces and not on the single interfaces that are part of the bridge.
A common recommendation is also to assign manually a MAC to the bridge interface.
Since they are not used anywhere, the categorization of interfaces is also redundant/unneeded, i.e. you can remove:
/interface list
add name=WAN
add name=LAN
/interface list member
add interface=wlan1 list=LAN
add interface=ether1 list=LAN
add interface=ether2 list=LAN
add interface=bridge1 list=LAN
(but this is only cosmetic)
[1] if you use (as you should) Winbox 3 to access that mAP, you don't even need to have an IP assigned, and connect via MAC instead:
BTW there are several reports of issues with Webfig with 7.20.4, yet another reason to use Winbox.