The signal you want isn't IP — it's one the visitor's browser already sends. Every request carries an Accept-Language header with the person's actual preferred languages, set by their own device. IP only tells you where someone is, not what they read: a Belgian could want Dutch, French or German, a traveler in Tokyo gets Japanese they can't read, and anyone on a VPN gets the VPN's country. That's why Amazon's IP-based switching is the version people complain about. IP-driven pages also tend to get indexed in the wrong language, since search crawlers mostly visit from US addresses.
Out of the box, Flarum handles this partway: members get the language saved in their settings, and a guest who picks one from the language switcher keeps it (it's remembered in a cookie). What core doesn't do is auto-detect for a first-time guest — they see the forum's default until they use the switcher.
So the extension idea is real, just aim it at the browser header instead of the IP: on a guest's first visit, read Accept-Language, match it against the language packs installed, set that locale, and keep the manual switcher for when the guess is wrong. Same result you're imagining, far more accurate, and no geolocation database to maintain.
Next time, please useProposals for such ideas that you wish were implemented.