To my knowledge, Windows has no built-in feature for this, but there are third party applications that will help you do the trick. In my experience, ForceBindIP has always worked quite nicely. It does exactly what it says on the tin: running a program through ForceBindIP will make sure it uses a specified interface.
In your case, it would be a matter of installing the program (or extracting the portable version) and running µTorrent using
ForceBindIP.exe 220.127.116.11 %PROGRAMFILES%\uTorrent\uTorrent.exe, replacing 18.104.22.168 with the address of the wireless interface.
In case there is no route from your wireless interface to the destination, you need to add one. It can be any route you want, but for an application such as µTorrent, you will probably want to route traffic to all destinations instead of specific IP ranges.
To do this, bring up the elevated command prompt, type
ipconfig and take note of the gateway of your wireless connection, which is probably the IP address of your access point (e.g. 192.168.2.1). Next, type
route print and check the two-digit identifier of your wireless card in the interface list (e.g. 12), as well as the metric of the 0.0.0.0 entry in the routing table. Then, add the route using:
route -p add 0.0.0.0 mask 0.0.0.0 192.168.2.1 metric 50 if 12.
The -p switch ensures the route survives a reboot, but it might still break if the wireless interface gets a new identifier. The '0.0.0.0 mask 0.0.0.0' means the route is valid for all destinations. '192.168.2.1' refers to the address of the gateway you want to use. 'Metric 50' adds a certain cost to this route and you'll want to set it well above the metric of the other 0.0.0.0 entry to avoid programs not bound to a given interface of using it instead of the wired connection. Finally, 'if 12' sets the interface to which the route applies.