Thanks. The nslookup tests show that the system you're on is correctly using Pi-hole for its DNS, and that Pi-hole is correctly returning 0.0.0.0 for that domain, since it's a known blocked domain.
If you're seeing Pi-hole bypassed when using your browser, check that your browser isn't using DNS-over-HTTPS or something like that, usually billed as a privacy feature. For example Firefox's info on their setting is here.
You should be able to see your computer's queries, and those from other computers and devices on your network, appearing in Pi-hole's Query Log.
The debug log all looks good. The diagnostic message about rate limits isn't in there unfortunately so I assume you cleared it beforehand. It should say which device is hitting the limit, and then you have to find out why that device is hammering the DNS [edit I see you found it]. You can look at its queries in the Query Log as a good way to get an idea of what it's doing. If it's trying to reach a blocked domain, it may be beneficial to whitelist that domain and let it reach it to see if that quietens it down.
Edit - actually there is one thing, your Pi OS is configured to use itself for DNS, ie it will be using Pi-hole.
-rw-r--r-- 1 root root 71 Feb 22 23:09 /etc/resolv.conf
search localdomain
nameserver 10.200.0.6
This will work, but it also means that if Pi-hole blocks something the OS needs during an update, or if Pi-hole needs something and that something is blocked, you might run into a catch-22 where you sort of lock yourself out. It's better practice to configure an external, trusted DNS provider for the OS itself. For example you might choose Quad9 or your ISP's DNS if you trust those.
You can edit them using sudo nmcli and navigating to the connnection, where you can Show and edit the IPv4 settings and the DNS servers for the OS to the external ones of your choosing. Pi-hole and Unbound are unaffected by this, it's just for the OS itself to use.