Sure it helps Joseph thank you for pointing me that example, it really different approach that mine,
I ask me a good question now, what is best method to use, the sleep Awake Event system or
The method that track what we are clicking on, and that benefit of this to reload all the switches status from the a save memblock from the disk.
i guess the second one is better if i understand it well.
I post you my personal approach : ( on pastebin again :))
http://pastebin.com/mJ9MrZX5
can be useful 
I must to weight cons and pro with the marcus’s method, because the switch code is a lot of extra linies to add , when my method just need a [mvarSet, pluginInt, 0,1 ] (when pressed ) or [mvarSet, pluginInt, 0,0 ] (when unpressed )
Does it impact the performance when sculpting or anything, if the Zbrush tick and wait for the proper event, to awake from the sleep mode ?
Into a game engine there is so many element that tick awaiting to be triggered, considering my own experience, i don’t think there will be more advantage if the code of the plugin increase with more lines of code (marcus method), as i can reduce the the timer to only tick at a low frequency my method, could really also make the difference, concerning the part of the code that reads the memblock then set each switch to the proper state, the code is equivalent to marcus 's method, I don’t think there is anything to compare here to measure the performance.
smaller is the code, and then the performance should be improved.
the problem is that i really must to take the correct decision on the engineering choice.
Thank you for taking your time to shed your light with me Joseph, i appreciate the help.
would you like to join ma beta tester list ? i could send you the toolset for evaluation i think you would appreciate it a lot 
If yes throw me you email in PM, i still have no date, but the first beta release is imminent 
Friendly,
Nicolas