Any evidence? I know I didn't give any for my case, but you have made quite a big statement.
egemen said so (indirectly) and SSTS proves that. For the original non SSTS leaktests Comodo gives warnings, but the SSTS ones with ring 3 unhooker are failed by Comodo, for example keyloggers.
Also, what do you mean by "unsecured"?
That the unhooker of SSTS can unhook them.
And impossible to do correctly (i.e. in kernel-mode) due to the fact that the shadow SSDT is protected by PatchGuard and MS doesn't provide any callbacks for win32k.
However, KIS catches the window message handles of SSTS on x64. So what?
What do you mean by "secured", and how secure can they get?
I don't know, ask the Outpost developers, hopefully they will share their secret with Comodo

Are they secure from people directly using the "syscall" instruction?
You are the expert, not me

Maybe you should look into the SC of SSTS and get your own impressions of how several products score on x64.