Is your feature request related to a problem? Please describe.
Maybe but that's not the (only) reason for my feature request. I have the expression I'm losing inbound Tor connections relative to clearnet connections once the default maximum of 125 connections is reached for a listening node

EDIT (almost 2 weeks after the creation of the issue):

I determine the number of inbound tor connections as:

bitcoin-cli getpeerinfo | jq '.[].addr' | grep 127.0.0.1 | wc -l

Note: I get 132 max connections because I add some outbound tor connections by hand.

Some statistics after restarting bitcoind:
date: total connections/inbound tor connections
14 juli: 100/17
16 juli: 120/15
22 juli: 131/10
24 juli: 130/7
25 juli: 130/5
26 juli: 132/4
27 juli: 129/3

So it's very likely I lose inbound tor connections once the maximum number of connections is reached. Please add the bug label.

Describe the solution you'd like
Allow to specify the number of Tor connections and clearnet connections separately. For example, numberOnion=25 would reserve 25 Tor connections of the default 125 maximum number of connections.

Describe alternatives you've considered
Fix the bug first :-)

Additional context
Maybe this issue should be split into 2 issues. One with the feature request and one describing the bug.