max_concurrent_http_announces - tracker status is "Updating" too long time

[postcd]

Linux, v. 4.3.1
Many trackers shows "Not working", It shows this even for the trackers that are working and many people has this problem in 4.2.x, 4.3.x https://github.com/qbittorrent/qBittorrent/issues/7762

I see that the http tracker has the Updating status for many minutes, even the timeout is set to like 8 seconds in Advanced options.
So i was assuming the qbt is slowing down announcing somehow and showing fake "Updating" status instead of "Queued for update"?

I seen this advanced config option:
max_concurrent_http_announces = 50
Explanation: limits the number of concurrent HTTP tracker announces. Once the limit is hit, tracker requests are queued and issued when an outstanding announce completes.
I see the GUI allows me to max out to 99, maybe i can add more by editing .config file manually.

But the question is why this low limit.
Because if i have 2000 torrents, i see that one http tracker is there maybe 1000 times. So i can imagine queue can be very long (i do not know how long or how to discover it or how to determine right value for the queue/limit so i do not worse the things.

At same time i am looking for the way to remove non working trackers from hundreds or thousands of torrents and obviously i do not want to do it one by one.
Again no one yet create an interface that would allow it:
viewtopic.php?f=10&t=4350&p=22544
https://github.com/rumanzo/qbtchangetracker
https://github.com/qbittorrent/qBittorrent/issues/12649

[postcd]

I have quit qbt and manually edited the qBittorrent.conf file (on Linux is in ~/.config/qBittorrent/) and adjusted conn. limit like this:
Session\MaxConcurrentHTTPAnnounces=700
(qbt GUI allows to set max. 99 while default is 50)
and my impression after this change is that:
1. i think that the http trackers quickly got Working status and i do not see any Updating ones.
2. i do not see any significant CPU, disk, network issue

Anyone have feedback regarding this change please or what to check to verify i am not doing bad move? I am on Linux.

[postcd]

i think that qbt may be resetting the number back to to 99 on quit or on modifying advanced options. Because it is unable to display my custom set value 700 and instead it reset it to 99 so on save, i accidentally return back to insufficient 99.

So i have adjusted my qbt Linux m0nitoring bash script to replace my variable 99 by new value before launching qbt:
sed -i "s|MaxConcurrentHTTPAnnounces=99|MaxConcurrentHTTPAnnounces=700|g" ~/.config/qBittorrent/qBittorrent.conf && qbittorrent &

[postcd]

Update: in 4.3.3 i see, i can set even 900 HTTP announces in Advanced config tab.