At some point it's on them to live with their choices. And just from my small sample size (I doubt there's a large sample anywhere), those people are more interested in complaining about their self-inflicted woes than engaging with the content.
/rant
I only noticed font choices when they were bad, since I started blocking custom fonts the web has become remarkably readable (and consistent).
Just add a font fallback.
Also, it's commonly recommended to load fonts asynchronously/deferred without blocking the main page render. But I HATE it when the page jumps around as it cycles through different fonts before the real one loads. I'd rather get dinged on PageSpeed insights with "Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path." rather than have everything popping about for the first second. Is it just me?
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/A...
I also had to make sure I was preloading my fonts properly... not sure if this is the same guide I followed, but it's close. The only difference is that I swapped that "&display=swap" to "&display=fallback":
Just now I learned of "font-family: monospace, monospace" hack. Indeed, browsers will render the font smaller with just one "monospace".
I've never run into it before because setting explicit font-size in pt or px avoids that weirdness.