Continuity is a personal choice for your PWS....
I suppose.
Perhaps you mean that you value altimeter above MSLP, and when you discovered the workaround (zeroing out elevation), you made the leap. If so, fair enough. That's something different than CWOP compliance vs. database integrity.
When I look on a weather map, however, I don't see altimeter. I see SLP. That's what meteorologists use to make forecasts. Given a properly calibrated sensor, I should be able to plot my SLP reading on a current weather map with a fair degree of accuracy (assuming isobars aren't too compressed and temperature assumptions are correct). Indeed, I can do that and that means the data I provide to the public via my website and other providers can be used for accurate forecasting, modeling and ground truth verification.
In any event, and not to put too fine a point on it, no one should have to choose a pressure type at the hardware level
just to accommodate CWOP given how long open source software solutions have been available. Suppose, for example, that CWOP expected temp in Celsius. Should the user have to change their console to Celsius just to accommodate a lazy developer who can't be troubled to convert from Fahrenheit before sending to CWOP? I suppose one could argue that preserving past temperatures is a personal choice, especially given how universal Celsius measurement is globally. I would counter argue that's a tangential issue in this particular discussion.