Not that you need to use route for anything trivial. Just installing a second interface and setting the IP address, netmask and broadcast address on the interface are enough for most cases.

It is entirely possible that stuff like this is crippled in Windows Home (or whatever they call it) and the like, I've only ever used it on pro versions of Windows (and even then I haven't needed to do it for a while).

Though I do still use route regularly still. When you need to access a client's secured network and only the IP address of the office broadband router has access, it is quick and easy to VPN into the office and then add a route for the client's server via the VPN.

(the VPN I use in this case isn't locked down at all)