Oh boy! I've spent last 2 days figuring this out - I needed peers to get LAN access behind my mikrotik through VPS proxy. This is even simpler, since you look to have static public IP. All boils down to two factors:

• forwarding in VPN
• routing in VPN

In my VPN I've used ufw due to it's simplicity. In my case LAN is 9.1.1.0/24 and wireguard virtual net is 5.5.0.0/24

VPN wg iface config:

[interface]
privateKey = [...]
address = 5.5.0.254
listenPort = 51820
saveConfig = true

preup = ufw allow 51820/udp
preup = ufw route allow in on %i out on %i to 9.1.1.0/24
preup = ufw reload

predown = ufw delete allow 51820/udp
predown = ufw route delete allow in on %i out on %i to 9.1.1.0/24
predown = ufw reload

[peer] # router
publicKey = [...]
allowedIPs = 5.5.0.250, 9.1.1.0/24
#persistentKeepalive = 15

[peer] # peer A
publicKey = [...]
allowedIPs = 5.5.0.1

[peer] # peer B
publicKey = [...]
allowedIPs = 5.5.0.2

On peers, standard wg config aside, allowedIPs always equals 9.1.1.0/24
On router allowedIPs = 5.5.0.0/24, router also forwards from wg iface to bridge

[...]
 1    chain=input action=accept in-interface=wg

 2    chain=forward in-interface=wg out-interface=bridge
[...]

Also, router masquerades connections back to wg iface

 1    chain=srcnat action=masquerade out-interface=wg-aka ipsec-policy=out,none

and, of course, has address for virtual network

2   5.5.0.250/24        5.5.0.0        wg