Hi Ronny,
easy question first: The Difference between "IP Socket Destination" and "IP TCP Port Destination" is that the first will match on both UDP and TCP, while "IP TCP/UDP Port Destination" only match their respective protocol.
As to your actual problem, I don't think building such a rule is possible. It seems like there is some kind of technical limitation as to how complex these policy rules can become.
If your clients are not residing in the same subnet as the SSH servers (192.168.1.0 in your example), I guess the easiest workaround would be to block those SSH connections with an ACL on their gateway.