That would still rely on

A) some kind of secret that only the server knows that the client can verify in order to ensure it's not trading nonces with the MITM.

B) A way for the client to ensure that the nonce isn't being passed through a second tcpcrypt session between the MITM and the server with the connection being in cleartext between the 2 tcpcrypt streams.

Currently the best supported method of implementing both A and B is certificates, which means you may as well use TLS.