hmm... feels like it's staring me right in the face, yet I cant see it.... almost like wg22 refuses to forward the packets, wierd....
what if you add a more specific rule in the forward chain, filter table just to monitor the packet count and validate that your pings are actually what we are seing:
(just execute directly from the router ssh prompt, it will be removed at first reboot or firewall reset, but we only need it for our test)
ip6tables -t filter -I FORWARD -s aa65:17b6:23ff:100::2 -o wg11 -j ACCEPT
this would count packets from address aa65:17b6:23ff:100::2 (your wg22 client) on it's way to wg11.
you could see it from the same command as before, should be right up on the top of the list.
then test again to ping some other internet ipv6, like 2600:: (this is usually ping-able) from your wg22 client and see if the count goes up.