[错误] 碰撞延迟与选优结果完全不同

** Bug description ** Please describe the bug clearly, including the observed abnormal behavior and the expected behavior. 1. The delay of Clash for Windows is significantly higher than the node delay displayed when optimizing. 2. The delay test of Clash Verge is significantly time-consuming. ** Expected behavior ** 1. The delay of Clash should be similar to the node delay displayed in the command line. 2. The results of Clash Verge should be the same as those of Clash. ** Steps to reproduce ** 1. Run the command Docker-compose exec warp-clash python3 app.py optimize 2. Click the Clash button Configuration Update Proxy Delay Detection 3. Click the Clash Verge button Subscribe Refresh Proxy Delay Detection ** Screenshots ** Left: The results after optimizing, updating subscriptions, and testing delays. Right: The results after optimizing. ------ Left: The results after optimizing, updating subscriptions, and testing delays. ------ Right: The results after optimizing. ** Environment information ** - Device model: Laptop - System version: Windows 11 24H2 26120.961 - Software name: Clash for Windows - Clash Verge - Software version: v2.0.39 - v1.6.6 - Subscription type: Automatically determined ** Additional information ** result.csv