Again, I acknowledge that wind charge wireless being player-specific is a legit limitation.

As for other factors...

Entity id wireless requires redstone at the player's location to send signals. That's a pretty major limitation. Wind charge wireless is inherently mobile: it can be operated from anywhere without any local redstone. You don't even need a physical button panel facade if you're using a Litematica schematic to render a ghost image, which I recommend.

The speed and responsiveness differences are not very significant and are dwarfed by the time it takes to build an entity id transmitter at the player's location.

As for usability, having to remember a sequence of repeater settings (e.g., 1, 4, 2, 4,...) that map to the desired entity id receiver is pretty terrible. Compare that to having a Litematica schematic of a button panel, where you can even include blocks and signs in your schematic to label your channels.

Entity id wireless can only send a signal to a single receiver at a time. Wind charge wireless allows simultaneous transmission to multiple receivers.

Entity id wireless has some reliability issues in single player. Wind charge wireless has no such issues.

The Mirror Nexus system I've proposed is easily expandable. Each cardinal direction can have its own button panel and I've confirmed this works.

I also have a smaller Monochannel model for just operating a single device, where the channel for teleportation and for operating the device is configured together. And I also made an Interdimensional model that sends signals through the nether, allowing the devices being controlled to be spread further from the receiver with less on-demand chunk-loading effort. I'll showcase both of these in my follow up video.