What knc1 said
.
By virtue of being an 'app', you can strike the KUAL stuff from the list of culprits: they only do something if you ask them to.
The JB, MKK & the Rescue Pack are both basically a single or a couple of files that don't do anything besides sitting there being useful, so, same deal.
CM is also a Kindlet, same bag as KUAL.
Python is, well, the Python interpreter, so, if you don't do anything with it, it doesn't do anything.
That leaves the ScreenSavers hack, which, in default mode, will churn a tiiiiny bit during boot, and then nada, and, if in cover mode, will churn a good deal for a few seconds when you open a book. If the book has already been opened once, the impact should be near-zero, though.
So, yeah, unless you spent your time opening new books like crazy in cover mode, none of what you have left should have any impact (even a non-significant one) on battery life.
TL;DR: usual culprits: Indexing, huge catalog (either of books or collections, the new 'Cloud Collections' stuff might have made things worse in regards to the performance impact of collections).
As usual in these instances, htop over SSH is your new best friend to investigate
.
As for the JBpatch entry, check your extensions folder, it should come from something in there that doesn't look like it belongs to what you still have left installed.