I'm not convinced that heimdall worked... The partition info it dumped just doesn't make much sense to me and seems wrong, somehow.
As for you getting one of these, it's a really great little tab, and you shouldn't let owning the 10.1 stop you. The 7" tablet fills a massive hole left between the too small phones and too large 10" tablets. I find its the ideal size for reading ebooks, quick games, and taking with me when I am running out. My 10" is an iPad, and I use that, mostly, for taking notes at work, but it's a bit cumbersome to carry with me everywhere. You have to admit, the 10" won't fit in your back pocket.
Anyway, I'd love to see your DD kernel ported here...
The portability is tempting - on the other hand, the ZAGGFolio keyboard on the 10.1 is REALLY nice, and the 10.1 is good for ease of use when I'm not carrying it.
I'd drop the 10.1 in a heartbeat if there were a 10" Exynos-based Tab.
As to DD porting - I don't know if that's going to be necessary. You seem to have the technical, analytical, and research skills it takes to move forward with development here on your own, with just a few tips regarding "samsungisms" to get you started.
Situations like this are why I try to make my git repo as clean and understandable as I can - so a developer for another device with similar architecture is able to move forward without having to reinvent the wheel. This frees them up to make new discoveries, and EVERYONE benefits. Remember - much of what initially went into Daily Driver came from Ninphetamine on the I9100 because Netarchy and Ninpo were similarly open about their developments and kept a clean git repo.
Keep in mind that other than some small tweaks to xdandroid's userland (GPS libs), the Samsung Infuse was my first major foray into Android development and I bought that device in late June. Fortunately the Infuse community was close-knit and had a high degree of developer communication/cooperation - we didn't have the prima donnas some communities have. It made for a great learning experience.
Tips going forward: While you've already been messing around in the initramfs to try and get recovery working, I suggest extracting a clean one from a zImage and posting it up to github. Then make commits as you integrate CWM.
Similarly, take your stock kernel sources and commit them to github BEFORE you make any changes. From there, do the requisite cleanups and .gitignores (see my repo for examples) and then start doing development. You should be able to "git am" quite a few of my patches against Daily Driver. As you go forward, try to (as I mention in my kernel thread) keep a "one feature = one commit" rule - or worst case "one feature = 2-3 commits" if you find yourself having to fix stuff after public testing. Avoid commits with multiple features at all costs. In fact, if you do get a multi-feature commit somewhere, try for your future sanity to split it up.
Avoid rebasing commits pushed to a public repo at all costs - NEVER do it for a major branch, it may be OK for a "side project" branch that no one uses (like the siyah_deltas branch I had on github for easier reading for a while).
Last, and few kernel devs do this - If you revert a commit using "git revert", add documentation on why you did it to the commit message.