@anonymint: You mentioned somewhere that your coins could be stolen during the hypothetical "segwit thief" even if you received them as legacy format transactions, because if these coins had ever been touched by a segwit transaction from that point it becomes susceptible for the attack? I think you also mentioned that the entirety of the wallet could be under risk. I cant find the quote.
Anyway what im saying is:
legacy->segwit->legacy = your coins are at risk?
I have been accepting some segwit transactions assuming said risk so I will be able to find if they ever magically move myself, but I don't get how the rest of the wallet could be under risk.
if I have addresses pre-segwit fork with bitcoins in it in a wallet.dat, and I generate some segwit addresses and store them there in the same wallet, given that I don't mix inputs when sending transactions (I use the nice "coin control" feature in Bitcoin Core for that) then I don't see how these pre-segwit fork coins could be at risk, since they haven't even moved since then.
What I don't get is how are you supposed to be sure that you are receiving a transaction that has a "clean", no-segwit history. This will be increasingly harder for any moving coins as time goes on, segwit is now 44% and rising. Honestly if that ever happens I have doubts if there would be a recovery from such a clusterfuck.