I do not think that event numbering is dynamic, not in the way device number is.
(After all, its an event source, not a device.
)
I have not look but I expect they are assigned in u-dev rules.
You could look there, or just play with some test code and plug/un-plug to see what is needed.
And I would suggest a "wait event" type of approach rather than any kind of looping test.
Keep in mind your Kindle only has a few hours of battery run time (the marketing pitch of weeks or months includes the time the device is asleep).
Also keep in mind that 'hack' is just a four letter word.