Fortunately, an upstream fix was submitted by Brave’s security team which led to both of these Web APIs to be fixed in Chromium relatively quickly. (#6249551 & #6269498)
There is one more way through which I was able to achieve the same impact (Leaking the user’s real IP address to a remote host behind Chrome VPN Extensions/Brave’s Tor window) which is unrelated to the BackgroundFetch/WebAuthn APIs. However that issue has yet to be fully resolved by all affected vendors, so sadly, I am not allowed to disclose it for now.