Three points:
1. Yeah, you're right the Davis terminology isn't ideal. It's obviously based around the idea that users buy a complete station rather than mix and match different (but perfectly compatible) components. If anything, I tend to think that the console type defines the station, since it's typically the console that formats data for sending to wl.com. So Envoy = VP2 in this context.
2. Davis have arrived at quite a complex platform in wl.com 2.0, at least in the sense of how many different combinations of station component and sensor types it has to deal with. eg there are 4 main types of 'sender', ie cell-based (EM and Connect) and logger-based (IP and WLv6) and these can be very different from one another, especially EM vs the rest and then Connect vs the two logger-based ones. As a result of the innumerable combinations and scenarios there still seem to be some wrinkles in the way 2.0 behaves with various edge cases that haven't been identified and sorted yet. So always worth an email to support@weatherlink.com to highlight any issues - if users don't tell them then they'll likely never know.
3. Specifically re VP2 transmitter IDs: I suspect this is only relevant to Connect systems. EM doesn't use these IDs and I'm not aware (BICBW - don't have a station still on 1.0 to check right now) that IP loggers and WLv6 even upload the ID information to wl.com because AFAIK there's no back-channel from wl.com to the console to change transmitter settings remotely. But Connect is different - there is no obviously no console to configure locally and so a back-channel had to be built into the Connect comms to allow remote configuration and hence Connect does show IDs.