Not directly related, but if the client supported a separate Truck, Car, Bike, Walking, Railroad flag, some of the Wazers using public transport or walking, could continue using their fave app without polluting the rest of the data.
Using this, Waze can safely discard the 'public transport' & walking data but still attribute the user points, milestones & edit area based on the 'rides'.
Waze could also then collect the 'averages' data differently for Bikers, Truckers and normal commuters by car, or at least separate trucks from Cars & Bikes.
Heavily loaded trucks pollute data averages for long-hauls, due to slower averages up hills or small inclines. Trucks also stop at compulsory Weigh Stations, where commuters don't.
Similarly, bikers pollute suburban commuter data by lane splitting on freeways & highways.
I'm not sure if truckers likely prefer the 'Major Routes' on long hauls, but I'm sure most of them have fixed routes that they use or are required to use if they are not privateers & part of a larger corporation. These will generally be the shorter (supposedly faster) routes, even if tolls apply.
All in-all, with some collected 'unique' averages with all stops etc. included, should easilyy show better or faster routes for specific vehicle types.
Something as simple as this can be done without relying on extra input from editors, but would obviously require Waze to store extra segment averages for different vehicle types & where data is absent, they would simply use existing averages.