I'm stuck at 1119999 again. It looks like -connect only restricts outbound connects, but will not disable inbound connects, so any peers on the wrong fork which you've communicated with previously will still be able to connect.

I think the only reliable way to properly upgrade may be to install a copy of the blockchain database from the correct chain. A checkpoint would probably not hurt, either.

This mess would probably not have happened if the KGW fork was properly scheduled!