A lot of our effort is concentrated on public transit routing, but many
people use OTP primarily as a bicycle planner. Contributers in Portland
spent quite some time tuning the interpretation of OSM tags to give good
bicycle routes. Other developers are currently working on making OTP a
viable planner for motorized vehicles.
So street modes (especially walking and bicycling) are part of OTP's
scope, and I wouldn't say OTP is particularly specialized in transit. We
did however decide to emphasize flexibility over speed in on-street
routing. There is a trade-off between personalized street preferences or
custom edge types and extremely fast pre-computation based algorithms
like contraction hierarchies. This is a trade-off between specialized
complexity and a more open system.
No, OTP is not optimized for giving driving directions instantaneously
over continental distances. It instead targets flexible multi-modal
itineraries at the regional scale, handling schedule-based transit modes
alongside on-street modes. On that basis, I'd say OTP is an good option
for this project. What you are describing could certainly be implemented
with OpenTripPlanner.
-Andrew