I suspect the high CPU process will be the Adobe ePub renderer or the ACCESS KePub renderer. If that's the case (assuming the info is accessible to NickelMenu scripts) it might be better to note which book is in use and the book position at the time and only note the process if it's not one of those.
Also, how are you defining "high CPU"? False positives are better than false negatives here, but too many false positives and it could quickly get too hard to use that log to track down which books or segments of books are causing problems.
|