Same device connects to different servers depending on setup

I am noticing interesting behavior around which server location is being used. I am located in the Great Lakes region of the US.

When using Private DNS in Android I connect to servers in Pittsburgh. This is slower and less reliable than Detroit and Chicago. Using browser private DNS in Windows, Android, and Linux, across all browsers (Firefox, Chrome, Brave, Edge, and Chromium all tested) connects to the same Pittsburgh servers.

Windows 11 setup with native DoH, and Linux setup using systemd-resolved, connect to Chicago. My router with asuswrt-merlin using native TLS also connect to those servers which are fast and reliable so no big issue there.

The Android app, Windows App, YogaDNS, and the cli app used in Windows 10/11, Linux, and router, all connect to the closest, fastest servers in Detroit which have been working great after some recent downtime.

Any idea why the private DNS implementations in browsers (tested in Android, Linux, and Windows 10/11) and Android would connect to servers that are not closer and faster? Either of the first two would be so much better.

Please note that I am talking about Private DNS in browsers and Android so the diagnostic tool may not provide the correct traceroute info needed.