Don't decrypt twice

According to #13328, the minion was stacktracing on state but operating
normally after that.

I believe this problem may have originated in the channel-reuse changes in
functionality into the transport, which would make it unecessary in the minion
method itself. (Please correct me if I'm wrong, of course. I'm making an
assumption here.)

At any rate, this removes that duplicate functionality, thus eliminating the
stack trace.

Closes #13328