@zandersig,
Thanks a lot man... I really appreciate it!!

I'm just happy that I'm able to offer assistance and help out.
The "Secure Boot - Enabled" is perfectly OK. It just means that the boot.img/kernel is protected.
You didn't know that the N5's birthday is 3/2/1970?
Thats when the first nexus line was being built.
Lol... I'm kidding

As Rxpert83 said it's really just a default and a bug in the recovery. Happens with some versions of TWRP and CWM.
If you update your TWRP to v2.7 and make a new nandroid backup it will fix the date issue and you can delete the old incorrect dated backup or if it bothers you, alternatively you can just rename the backup or you can follow this method to correct the date... It's lengthy thought just to correct the date issue -
[TOOL] Fix TWRP Backup Dates / Find Your Pho… | Google Nexus 5 | xda-developers
I think making a new backup with the updated version of TWRP is easier thought and you can test out your adb and fastboot setup.
Ok. To check and see if the "Nexus 4 adb interface" is working, connect to your PC with USB debugging enabled, open command prompt and type:
adb devices
The PC will list the devices attached with a long serial number.
In fact this would be a great point to test and to flash the TWRP 2.7 from Hook. See post #39, Download the new TWRP and put it in the "platform tools" folder. Rename the TWRP to just "recovery.img" (without the quotes) Then open command prompt and type:
adb devices
If everything is working properly it will list the adb devices attached, then type:
adb reboot fastboot
Device will reboot to fastboot mode
Then type:
fastboot devices
This will make sure that fastboot is working properly and will list the fastboot devices attached.
Then type:
fastboot flash recovery recovery.img
Then it will flash the new TWRP v2.7 over the existing recovery and you'll be good to go. At this point you can reboot to recovery and make a new backup with the correct date.