FOR FUTURE THREAD HUNTERS AND INTREPID PROBLEM SOLVERS... THIS HAS BEEN SOLVED
As JorgeB suggested there were VM's autostarting, but I couldn't get to the VM screen to turn them off before it would freeze up.
To remedy autostarting from CLI (within /mnt/user/domains):
$mv yourVM/yourdisk.img disabled_yourVM/yourdisk.img
This didn't solve the problem but it may solve yours.
What was ACTUALLY my PROBLEM was that the system/libvirt/libvirt.img file must've been bad. I deleted it from the advanced settings in VM Manager and now I need to rebuild all my VM xml files BUT it solved my problem! I can now enable VM services without immediately borking my server. At least this gives me a point to rebuild from vs being entirely unable to even interface with the server because it starts screaming as soon as I enable VM Manager
LESSON BEING CRITICAL BACKUPS FOR SERVICES -- APPDATA DOMAINS SYSTEM
My previous backup method of an external usb drive which got disabled because it was unplugged when the server was moved briefly to change the attic air filter so my backups are too far out of date to be useful. New server will have raidz pools in cache so I can snapshot everything to the array and also rsync it to somewhere else.