Those two can be rewritten into one point. The obvious solution, which I've been telling you about is, prioritizing native -> SW and SW -> SW transactions.
segwit only = bigger block ONLY IF:
1. users move funds to segwit keys
Which is guaranteed to happen
LOL guaranteed. LOL
do pools prioritise LEAN transactions to allow more transactions in.. nope
do pools prioritise mature transactions to evade spammers.. nope
(spam: those that intentionally respend every block)do pools prioritise transactions with fee.. nope
(empty blocks/btcc zero fee confirm)you HOPE and have FAITH that pools will.. but 65% of pools are abstaining or saying no to wanting to prioritise segwit as a protocol. so they are not going to prioritise segwit transactions.
in short. no guarantee, no fix. just gesture, half expectations and faith
much like the expectation of
"if pools prioritise lean tx's we can get 7tx/s 2009-2017".. yet in last 8 years never had a block of 7tx/s
yes on testnet it can be seen but thats test net where 1 person is creating the tx's in a certain agenda display of expectation.. when dealing with real world people using it for real world needs. reality does not reach expectation or hope
P.S your "2.1mb" expectation is the exact same 7tx/s expectation that has been promoted since 2009.. but never reached
its all if's maybe's half gestures hopes faith trust.. not actual real rules that enforce it