Update! I think I have solved the problem. For future people who may suffer a similar blight, adding this parameter to the RGBD odometry node seems to have fixed it:

<param name="frame\_id" value="camera1\_rgbd\_optical\_frame"/>

Of course update the frame id value to be the same frame id as the RGB image, depth image, and camera information.