I'm not understanding the guidance.
For 1b I continue to think the guidance should be to use the road type appropriate to the road and mark all entrance segments as restricted to all but the allowed HOV vehicles. I don't see any rush to change from parking lot roads to HOV restrictions, but the guidance should be to use HOV restrictions as that is clearly where waze is going. There are disadvantages with parking lot roads. They prevent routing all the time, so they are now inappropriate for time-restricted HOV lanes (e.g. HOV from 7:00 to 9:30 AM). Such lanes should be time/vehicle restricted so that waze will route on them the rest of the time. Parking lot roads are also much more likely to be used a routing destination than freeway segments. Thus, if you have a parking lot HOV road running up the middle of a freeway and there is a destination pin nearer to the freeway than adjacent parking lot roads, waze may route to HOV lanes. This is less likely to occur if the HOV lanes are also freeway type.
For 2a, same thing, I think HOV restrictions should be used rather than PLR.
For 2b I do not understand the note:
Drivers who are not permitted to use the lanes may be routed by Waze via them, but it is up to the driver to obey traffic laws, and Waze will successfully re-route around them when the driver does not enter the special lane.
If the lanes are restricted to HOV only waze will not route onto them. They may be used if waze recalculates a route starting on them either because the wazer is driving on them or because of GPS error. But one should never get a turn instruction to take the HOV lanes.
Some HOV lanes go back and forth between being less than and more than 10-15m from the regular lanes. Currently I would read the guidance to mean such roads should not be mapped as they are not almost always over 10-15m away from the standard lanes. But you still get map problems and sometimes recalculation issues (sometimes to the opposite direction lanes) even if you only are separated significantly from the regular lanes for a relatively short distance. I think the "almont always" should go with the minimal separation so that lanes that vary between minimal and significant are treated as significant separation.
Under future support the following are still listed:
The ability to change the direction of the car pool lane automatically based on time of day and day of week. This is also necessary for other roads
The ability to set the minimum passenger count to zero (meaning the road is open to all drivers) based on time of day and day of week
These are currently supported in the editor.