Your question seems to be answered on Apple Stack Exchange. Note that the patch mentioned there seems to be no longer maintained, so it may have security issues if you do not backport fixes. A more up-to-date patch (supporting OpenSSH 7.6 as of this answer) is available on GitHub.* This particular obfuscated protocol is explained in more detail on its site. Judging by a quick read of the patch, this particular obfuscation seems to add a random length of padding to packets and encrypt the handshake using a preshared key stored in the configuration file of both the client and server. It is not particularly advanced, but will likely hamper automated protocol detection.
There are other ways to obfuscate SSH traffic as well. You could create an obfuscated VPN tunnel between the client and server and connect with SSH through that. I explained in another answer how to prevent OpenVPN traffic from being detected as such. You could use the techniques outlined in it (static keys and obfsproxy) to create a tunnel through which SSH can run. You need only a basic understanding of networking to bring up a virtual interface for the tunnels and assign a local IP to it so you can connect using your SSH utility. You can also use obfsproxy directly on SSH.
It's important to remember that, while protocol obfuscation can make automated detection or censorship more difficult, it does little to prevent an intelligent analyst with access to traffic dumps from realizing that the traffic is OpenSSH traffic. There is not much you can do to protect against such a threat while maintaining usability. All obfuscation does is raise the bar for detection.
* Applying a patch requires you know how to compile software from source code. You download the source code for the exact version targeted by the patch, and use a command to apply the patch, such as the