This is a great tip, although I don't think that explains why OpenVPN has the same issue on this laptop I'm typing from right now.
Even the official clean OpenVPN app has its own sense of up and down tunnels, which could cause similar problems. Wireguard, at least in its official linux implementation, is much lighter weight and if necessary reestablishes an active session on demand (whenever there's traffic) without any interface-level tweaks. That's probably invisible to applications, or at least much less visible even if there are low-level syscalls that can inspect the state of a wg tunnel interface.