No, my comment was about trying to secure something by hiding it. Encryption is not at all what I am talking about, I can't even imagine how one would "hide" via encryption.
A real world example is those who share a folder, but make it a hidden share, yet give the EVERYONE group full control on the security tab. I have seen some people "share" to everyone, but lock down security. MS recommendations are to share it to those who need it, and to lock down security as well. If all you do is leave the directory wide open, and add a $ sign to the share name, nobody can easily see it, but that doesn't prevent access. Especially when talking about vendor software, a vendor that shares a folder as part of implementation will tend to use the same share name across customers, so once you know what it is, you can use it everywhere.
Where it can be confusing is when you do something like rename the Administrator account. That is obscurity and not real useful if you set the password to "password". On the other hand, renaming it and using a secure password is useful. Just a secure password is useful. Why do I view this different than changing a port? Because a port scanner can be run on a different machine and elicit all of your SQL Servers, a simple program cab be written to scan every port and then determine what is running on that port. In order to get a list of account names, you first must access the box. Essentially, without the account name, you are going to have to try random account names, and then random passwords for each one.
Changing a port has no security value.