we want to allow config precedence over ssh settings. other than host, the ssh settings will not apply to winrm

I was testing the latest Transform on Hyper-V and VirtualBox tonight and found a problem with Hyper-V. Since all settings are fed from vagrant ssh-config, most were wrong for my box. I use a different username and password than 'vagrant'  and they were not being used and kitchen was trying to talk to winrm on port 22 since that is indeed the port that shows up in ssh-config. We dont see this problem on VirtualBox since it uses a different strategy for getting the port and in my case I do use the standard vagrant user on my virtualbox box but its certainly possible someone else could use a different user.

I'm not sure if I understand this..  Let me explain in words:

What I get is that if you don't have a `port` configured, it will search for `guest_port` (which I didn't know it existed) that for what I read it will act as an override of the `default_port` for the `Transport`. I don't see value in that.. :( Or maybe I am not getting it.

Isn't easier if we say; use the `config[:port]` if not_exist then use the `default_port` from the `Transport` and let `refresh_forwarded_port` to search for the right port?

In which cases do we want/need this?