I set up Unbound using that guide. It works great. Follow the guide methodically all the way through. Once done, you will have turned off Quad9 and will be using your own Unbound instance on localhost as the only upstream DNS for Pi-hole.
Doing this means that you are no longer sending your domain lookups to Quad9. You will be performing them recursively yourself from your Pi-hole device.
This gives you more privacy since there is no third-party able to see your lookups. Quad9 appears to have a good stance on privacy (doesn't log IP addresses, mainly counts query types), while Google stores temporary and permanent logs as detailed in their privacy policy.
If you are making use of Quad9's filtered DNS services you would lose that, so something to consider.
If you configure unbound as a recursive server, it will go directly to the authoritative nameservers and not use Quad9.
If you still want to use Quad 9 with unbound, configure unbound as a forwarding resolver. The following lines added to the unbound Pi-hole configuration file will set up unbound to forward (using TLS) all queries to Quad 9.