ArcGIS Pro: Most Cumbersome
Good catch. My bad. 
Note that 'V' is taken in Pro and we will need to find a new hotkey for activating this behavior, of course it will be customize-able, as all hot keys are. Also the option of using the XOR pen as we did in ArcMap to guarantee visibility is not possible in Pro so instead we will probably need to expose a marker symbol configuration so users can pick what marker symbol they use to symbolize the vertices with (whether that is a full symbol in the symbol model or a restricted symbol that can be drawn entirely on the video card is an open question). Currently we don't have a setting to override sketch vertex symbology (green & red boxes) but that is also desired. Trying to get a better idea about user expectations would it be sufficient to show vertices only of visible/snappable layers or do we need to include all visible layers (including non-snapable) layers?
Also we need to decide how far to show vertices. ArcMap would show all vertices for features that are close to the cursor (several pixels) but not all vertices of all features on the map. I'd like to only show those vertices close to the mouse (maybe 3x or 5x snapping tolerance, if we used just the snapping tolerance we could use the snapping cache to fulfill requests and it would be much faster but probably that isn't far enough 
). I find it confusing that ArcMap will show some vertices clear across the map from the cursor because they are part of a feature that is also close to the mouse but won't show other vertices relatively close to the mouse (much closer than the ones that are being shown).
Personally I just haven't see much benefit in the V key as the snap tips indicating that I'm over a vertex are good enough, its rather obvious where corners are so its mainly about discovering vertices that are close to 180 degrees and it isn't clear why finding a vertex is important (I tend to think of edge snapping as just as good).. In cases where it can matter (Utility Network and Network datasets) we follow the rules of those datasets to insert vertices at edge intersections where appropriate. I have always found the ability of the renderer to place markers at vertices in a more permanent fashion more useful and controllable (I wouldn't turn it on and off often, I would just author the layer for how I expect to see the data while editing (in a dedicated map that is symbolized for the purpose of digitizing).
