After running into this issue multiple times, the best workflow to circumvent the actual problem is just using my text editor of choice and opening the crontabs' full path:

micro /var/spool/cron/foo