Well, I certainly didn't see the professor as a utility, but yes, with regards to the package it does not make any difference. Just wonder what kind of properties we'd assign to him ;). Which brings in a different thing for the package: Linking of existing objects to utilities.
Wasn't there talk about a general scheduling package for Objects? If this is the case, we could split the reservations from the utilities and have a utilities package, that keeps track of the utilities and their properties, and a scheduling package, that allows reservations for any object within OpenACS.