For example, bicycles. We know people use Waze on bicycles, so if we have a bicycle option for them to pick, I bet they are more likely to do so. Especially if it makes their icon into a bicycle
They don't need to know the details that it behaves the same as if they picked "other" and we and Waze don't need to do anything beyond setting up the "other" option.
And if sometime in the future we actually do support bicycles in a more complex manner, then the backend can change and the client already is set to bicycle.
Yeah, give them an option "bicycle" and an icon. Even if this doesn't do a thing, in every town you will have 2 or 3 fanatic cyclists that will take that as an encouragement to map cycleroads. These 2 or 3 are the only customers waze will win by this - and probably the last customers, too.
I have often scolded Amsterdam cyclists for screwing up directions. I seriously thought that I would find hordes of them - hey, Amsterdam is the bicycle capital of the world. Careful study of the damage and patterns over the last weeks shows that all the damage by cycles in Amsterdam comes from a handful. I estimate now that far less than 5% of rides are bicycles. That is enough to screw up the map every couple of weeks and that is about half of the gain Waze can get from supporting cyclists in Amsterdam.
Google now supports bicycles. I looked at their map in my hood, and it is far from correct for cycles. It would take about twice as much change to do it right. All that for the benefit of a handful.... do the math.
Trucks and cabs, on the other hand, only need a handful of changes to existing roads (mostly) to make them completely happy. They spend all their working hours in traffic, adding benefit for Waze.