Its unusual for this thread to be silent for more than a day with my posts as an exception. i was chatting with a good friend of mine yesterday. he agrees that the biggest canidate to your error is that for whatever reason, your device is not able to create the dalvik cache which in return means many critical files will fail to load into the system properly resulting in a splash screen form of a bootloop. when he noted TWRP was the recovery, he showed me one of his older phone logs which looked eerily similar (it was another lg device of some kind that isnt very common except among prepaid users that he was working on), along with a log of the flash with CWM. in this case however, he had to semi dirty hack the vendor drivers and was using AOKP as a base. WHile this doesnt mean that TWRP is to blame, a test with multiple recoveries should be made. since i cannot GIT, i cannot ask for source and compile myself. I can however share you my email in pm in order to test your "nightlies" on my device. I have a TWRP backup of my current system, as well as a CWM backup, so i can simply wipe my device, re dd my recoveries, and restore backups no problem. another thing that was discussed was the fact you were restoring backups from another persons device. while the general rule of thumb is this will typically work, other issues arise in doing so, such as device dependait files get flashed in the process sometimes, rendering you with partially working restores, or in worst case scenarios, bootloops due to device inconsistancies.
When we are sucessful in building a bootable CM( rom, I would like to request a tablet style version that strips the phone capabilities of this device in favor of wifi, gps, NFC, and bluetooth only (disableing the radio entirely to avoid battery loss due to not being able to disable the phone signal only, as currently the only way i know to stop cell tower communication is through airplane mode that disables all wireless communications). I will also add a few additional tweaks and modifications to CM9 that would be very useful in a final build to make this phone really shine, some of which work very well on stock, and some that only partially work due to LG modifications. Some you can even view immediately: xposed framework which adds quite a few power tools that normally have to be hard coded in a developing rom, the viper audio driver which has massively improved the audio quality on my phone, a few resource scripts, one of which is the "supercharger" script that tweaks many setting that improve performance (has been useful in doubleing the battery life of my phone and the responsiveness of apps).
Edit: nice to see some new logs. MIUI i will have to go over later as it is quite different. as for CM 10.1, it is to be expected on some of those errors, but the main persistance is the lack of dalvik cache once again. other errors aside, this is killing the boot.
Edit 2: im quite tired of scratching my head all over this. im taking the splash screen cm9 log into a cyanogenmod irc chat room and gonna fish for answers. its better to get answers from the horses mouth than to try to pick my brain and my friends brain since we are both better on internal mods than core mods. (internal being working on a compiled system vs making a rom)
Edit 3: Brandon i need a copy of the cm9 rom. we might have a CM dev who is going to look at it.
Edit 4: Search Playfulgod on github, and pull his lucid or connect repos. he mentioned that would be our best bet to smoothing some issues out. DUE NOTE THAT the screens are shared between lucid and connect, but our viper is the oddball. this will need to be tread cautiously. if you dont pull the screen related files from our little viper, it probably wont work. also, he suggested using CM 10 instead of CM 9 and CM 10.1
Facebook
Twitter
Instagram