Some Cirque products do support remote wake, and some don't. So it is quite possible that specific product doesn't. If so, very sorry about that.
In terms of the setup inside the PC, Microsoft has made this a bit of a moving target, and I'm pretty sure somethings released as part of Win 10 make it into updates of Win 7. So let me say that generally, the requirements are that power must be maintained, and remote wake must be allowed.
It sounds like you have done a thorough and complete job of making sure the port stays powered. Although I would point out that Windows can decide to do different things with the port depending on what device is plugged into it.
When I'm checking out this stuff, in addition to anything the driver supports--which is usually nothing for power management--I do this. I open device manager and find my device. After I have found it, I unplug it and plug it in again and watch it come and go, just to be sure it is really the right device. (Of course you can't do that with an internal device.) Then I select the device and switch View/Devices by connection. (Having the device stay visible and selected is a Win 10 feature that might not be propagated to Win 7. If my device doesn't stay visible I have to find it, which can be quite tough.) The reason for finding my device in this view, is that I want to see all the upstream devices and see if they have any settings I need to fix.
When I do this with my "Dell Touchpad" which happens to be a Cirque/|Alps PS2 device, I can see that there are no power settings on it, nor are there any on the LPC controller above it. (The next device up is PCI Root and that is past far enough.)
When I do this with another device--USB "HID-compliant mouse" this time, there is a Power Management tab on the device itself, with check boxes for Allow to turn off AND Allow to wake. This is true for the mouse device, AS WELL as the "USB Input Device" above it. IMPORTANTLY, it is also true for the "Generic USB Hub" and "USB Root Hub" above that. As I recall, you must have Allow to turn off NOT checked for the entire path--all devices from the device itself to the root hub, and you must have the mouse itself with Allow to wake checked, in order for remote wake to work.
As I said, I'm not sure how much Win 7 has been updated to this (somewhat) reasonable behavior, but the general strategy is good.
As I recall, if the device itself doesn't support remote wake, the Allow to wake check box won't be there on the device. (I'm not sure about when it is grayed out--I think this is if it is expected to be powered down so it can't.)
And--caveat--it is quite possible some device above doesn't work as well as advertised. As Scott points out, some systems power down ports whether you want them to or not. Some systems keep ports powered so they can be used to charge, but power cycle them at some point, which resets a device so it no longer has remote wake enabled. (As I said, I think you excluded this possibility already in this case.)