What are you trying to accomplish?
Theoretically, you can configure a server application to listen on any port. Conceptually, the client can make a request to any destination port. However, the client and server must communicate using the same protocol. The BIG-IP is configured by default to listen on port 443 with Apache. The server expects the client to establish an SSL connection and then use either HTTP or the iControl API (based on SOAP) to communicate. The BIG-IP wouldn't handle an SSH connection attempt on port 443 though. Apache would reject the request as it's not a valid SSL request.
I think what you might have read about was creating SSL tunnels. You can use PuTTY or other SSH tools to create an SSH tunnel and pipe through an unencrypted protocol. Here is a wiki page on tunneling (
Click here). I can't see any reason you'd want to do this administer the BIG-IP though.
Aaron