Are you using the "-d" option to avoid trying to DNS translate addresses?
tracing with the "-d" parameter is fast, but "tracert (exemple)" that's the standard command I always run.
A slow DNS could be contributing to your slowness.
I'll repeat myself here in this forum thread as well.
There is another Windows 10 LTSC 1809 OS Build 17763.6293 computer nearby and everything is fine there. They are both connected to the same network, use the same DNS that are registered in the router. By the way, Traceroute also works without problems in the router.
If I install a Windows 10 image with older updates (with an older build), then the "tracert (exemple)" tracing goes perfectly, but some days pass (1-7... days), the updates are downloaded (they are downloaded/installed automatically, I only sometimes need to reboot the computer) and the tracing becomes slow.
I specifically deleted my old Windows 10 LTSC 21H2 for testing and installed a new 10 Pro 22H2 OS Build 19045.4780 (currently 19045.4894), at the first launch I connected to the network and made a trace, it was already slow. Therefore, I am sure that some update introduced these "settings". But is it possible to fix this, as kerberos_20 writes, it is not entirely possible. Or maybe these "settings" can somehow be fixed in Windows Defender (what exactly should I check)? Or is this some kind of conflict with the software? Connecting to the network either by cable or by WiFi does not change the results.