sadly though i appreciate the thought, my paypal wont allow me to accept money of any kind. they want a bank account attached to it, and i dont have a bank account... so the money just sits there and eventually reverts back to the donator. tried it before, really pissed me off lol
anyway, ill give you the rundown but i cant give you specifics on how difficult any varying cm will be because ive never built a working cm for a 3.4 zte kernel before
the possibilities are technically endless, if you can make it work. the extent of the kernel hacking necessary to make kitkat work right though is unknown. most companies use proprietary commands and variables for things, what samsung calls AAAA zte might call AAAB or AAAA_ZTE and sony might call AAAC etc. and then there are variances in the way things are called, samsung might use 2x2=4 while zte uses 1+1+1+1=4 and sony uses 2+2=4, which can confuse android at times. the main issue is going to be kernel headers, also called includes, signified with a .h file extension. those are pieces pulled from the kernel at build time, that tell android necessary values for things like framebuffer, which keeps stuff from overlapping and making the screen act stupid and jumpy. in essence getting the screen size... but its slightly more complex than that
the easiest one to build is probably going to be cm10-10.1 but i could be wrong, they work better on older devices with lower end adrenos, have different setups for things like storage, and every time android changes the things needed from those header files change slightly, or sometimes dramatically, meaning the headers need to be manually updated to build right
also cm11(kitkat) has started to use all this selinux crap i have yet to deal with, so i cant say for sure its going to be the most horrible experience of your life trying to upgrade the kernel for compatibility, but i would assume it will be no picnic