For the more common options we don't want to deal with fully supporting, just have them be pointers to the "Other vehicle" option that gets its speed ignored.
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.
So to expand that thought, once we have a list of vehicle types we can imagine people using, add ALL of the common ones in that list and point them to "other" until such time that they do get special treatment. If we rather NOT ignore their data as if they were "other", point them instead to the normal/default/car profile on the backend.
And in the bright and distant future, we could go crazy and have the client show 50 different vehicle types but the back end can have them assigned to a nice tidy list of 5 or 10 profiles.