It seems it was not about the Internet, but about the fact that I could not access the router. If I could connect to the router without getting up from my chair, then even without the Internet, through the local network, I could roll back the changes.
Who disappeared? You never deigned to read exactly how I set up the router? Because you can help me if you don't want to listen to me. Or maybe you did not want to help from the very beginning?
There's no reason why changing a Wireguard setting would break access to the router OS at 192.168.1.1 except that after applying any network changes, the router's Ethernet ports and wifi will drop carrier for a time and then start back up. If your PC is connected directly to router Ethernet or wifi, you may need to click the network menu on the PC and tell it to reconnect. If you have the PC configured to automatically connect to other networks, during the drop it may connect and stay there instead of to your router.
Maybe we should start with a very specific question:
Why do you want to use VPN? What is the intent of this connection? Are you trying to send all of your traffic through a VPN (for example: for privacy from your ISP or geo-location reasons)? Or are you trying to send only certain traffic through the tunnel? Or are you trying to setup a VPN 'server' to allow remote access to your network while you are out of your home?
Some time is how much? When everything is in order, then in about a minute, a maximum of two, the router restarts, and the page of the router 192.168.1.1 itself is updated. I don't need to do anything. And in this case, I waited about 10 minutes, and even the browser was "tired of waiting" and wrote that the restart was taking longer than usual. I had to go to the router in another room and restart it again. Only then did I get access to it...
As for the top level problem I would approach this not by destination IP, but by having two networks: one that always goes by VPN and one that never does. Connect endpoint devices to the one that meets the situation.
(Btw @mk24 and @psherman - #1 I see IPv6 addresses in the config, CloudFlare issues a /128, those won't work with default OpenWrt. And #2 my understanding is CloudFlare is still in the same geographic location -so the OP might not be able to circumvent the problem.)
(The OP noted they wanted to test to removed the "whitelist" so...#1 seems to have been wokring and #2 TV still didn't work with WARP.)
(Lastly, the OP never explained any of this, it was all guess-work.)