After an installation of the mullvad browser, I used it to access a simple archiving site which I was unable to access with firefox, palemoon, brave, librewolf, min and ungoogled chrome. The only browsers I could access the site with were tor and mullvad. Tor was typically like treacle to work with, but mullvad was as brisk as any of the other browsers mentioned.
I had contact with the website's creator and he assured me that all of the certificates and authorisations were up to date. With the other browsers I mentioned I kept receiving messages like: ERR_SSL_PROTOCOL_ERROR, or PR_END_OF_FILE_ERROR within a "Malicious Content" page. It made no sense to me after being assured by the website creator that the relevant matters were all in order. The site itself is simply a collection of non-controversial photos of meetings, camping activities and texts for an organisation creating an archive for itself. He uses MS and had no trouble with his browsers. He downloaded firefox to check, and also received the "Malicious Content" pages that I had. It has been a baffling matter, but mullvad has been the solution. It's too early for me to determine what the configuration differences are which have enabled mullvad to work in this case, but I'm very interested.
Edit: The conundrum appears to be resolved by this text from my ISP (Telstra) :
Telstra Broadband Protect won’t work if you’re internet connection is through a:
non-Telstra DNS network
VPN
proxy server
mullvad evidently uses one or more of those. The "Broadband Protect" appears to be overzealous in my case.
Second Edit: It's possible to have the ISP's "Broadband Protect" turned off by contacting them personally and requesting it. That has been done now, and ironically, it may make mullvad redundant in this matter, but it may still be quite useful in others that arise in the future.
Third Edit: During the first call to the ISP, the consultant said that she had disabled the "Broadband Protect" shield on my line, and it would be gone within an hour. Four hours later, it hadn't been lifted, so I contacted the ISP once more and spoke to a second consultant. He hadn't heard of this feature of the ISP, so he contacted a manager who informed him of what he needed to do. Evidently the first consultant hadn't followed through the disabling to its conclusion, and the process was cancelled. The second consultant explained how it was a complicated process involving fifteen steps to disable the shield, and asked me to wait on the phone for about ten minutes. His work was successful.
If I hadn't bothered with this, then at least mullvad would have been the answer.