I'm closer to Kevin's position. with a /32 it is a host route, but as to assigning it to a host - that would be a tentative NO!.

Assigning it to an interface means there is no room in the "subnet" for a router, so giving that address to a host without some assumptions on the part of other devices would not actually function. I suppose it could be linked in with mobile IP, and the host sends a gratuitous arp. The router would need to know to accept that, even though the IP address may be outside the subnet, and to add that /32 to the routing table. Access from the device would need to be by assuming everything to be local and proxy arp.

Where it may be of use though is an internal address for a server (a little like using a loopback on a router) that is multi homed. One interface on one subnet, one interface on another subnet, and the /32 is accessible via either. The would involve a degree of care with the connectivity. For that to have a point, the normal position would be for the server to participate in the routing protocol - eg RIP2 or OSPF. That may not be what the network people like - having an end system participate in routing may be considered a security issue. If one does not want the server to participate, you would need to use (floating) static routes. You would then probably want to connect the server to L3 ports on the switch, so that if the NIC or the cable fails, the network the server is connected to will go down, and take that static out of the routing table.