I was able to determine that the second error is just a symptom of the deeper issue. It's saying there are illegal paths in the field because when attempting to get the class ID it returns an error which it uses for the address of the link.
So the second error is a red herring and the real issue lies within the fact that for some reason the responsive design modules class id is not getting loaded. As it's key is clearly visible in the various config files.
Though I feel without some support it will be very tough to determine what has happened on the backend. From everything I have read my hunch would be it trying to load the class ID twice resulting in ambiguity and causing the issues. but that is nothing more than a hunch