First
We should consider the fact that bc1q addresses are mostly supported by most wallets, only few wallets are supporting pay-to-tap-root addresses for now. Even on many wallets that support both, bc1q is the default.
Second
Transaction in virtual bytes for segwit address (bc1q addresses) for 1 input and 1 output is 109.5
Transaction in virtual bytes for segwit address (bc1p addresses) for 1 input and 1 output is 111
Can you see how close they are.
Let us increase the output
Transaction in virtual bytes for segwit address (bc1q addresses) for 1 input and 2 outputs is 140.5
Transaction in virtual bytes for segwit address (bc1p addresses) for 1 input and 2 outputs is 154
Can you see how increase in output is increasing the vbyte which means increase in fee that would be paid.
Let us go for 10 outputs
Transaction in virtual bytes for segwit address (bc1q addresses) for 1 input and 10 outputs is 388.5
Transaction in virtual bytes for segwit address (bc1p addresses) for 1 input and 10 outputs is 498
Can you see how increase in output is making pay-to-tap-root transaction to be more expensive? If I am a campaign manager, paying many participants, I will prefer going for bc1q addresses (I mean segwit version 0 that you mean as segwit in your post)
Segwit version 0 has reduced output vsize
Pay-to-tap-root has reduced input vsize.
You can use this calculator to confirm that: https://bitcoinops.org/en/tools/calc-size/
Which means for more outputs, bc1q addresses have lower fee, but for more inputs, bc1p (pay-to-tap-root) has lower transaction fee. You can do that calculation yourself with my explanation using the correct formula, or you can use this tool for it:
https://jlopp.github.io/bitcoin-transaction-size-calculator/
Pay-to-tap-root would be good for input consolidation because it is of low fee if compared to bc1q addresses.
Segwit version 0 is of low fee enough, but version 1 (pay-to-tap-root) is of low fee when it comes to input consolidation and P2TR multisig transaction.