Yeah, that's a bit of a downside but also internally consistent with the approach of webfontloader, I guess. Ideally WFL would have the ability to flawlessly detect the outermost bounds of web font support and say "there's no possible way that this browser could support web fonts, so I don't even have to ask the module". But in reality, that's not really feasible, and some modules may want to just try to load fonts regardless of what WFL detects for browser support. (Maybe the UA is just wrong or unrecognized, for example.)

So yeah, I think this is a good change overall.