In this particular case, I was on the version for which the bug was initially reported. It is because
that I use ethtool in the startup script to disable Energy Efficient Ethernet (among other parameters) on both adapters (which re-initiallizes them) that I never experienced the issue. When WAN comes back up after ethtool finishes, it triggers https-dns-proxy to restart on it's own; effectively working around the issue.
Even if I did upgrade to the version that was just released though, it would not be a relevant test since my startup configuration already works around the issue.