> Unlike su or sudo this tool would exec to replace the current process (so it would receive signals ..etc.)
Where did you get the idea that su or sudo spawn a child processes for commands to run? I would be very, very wary of any security-sensitive code from author who didn't get such a basic thing right.
Unless you do very magic thing and replace my current shell, which would be the parent process of your command.