The community keeps emailing me and asking me to update this post and mark it as answered if I have an answer. The problem is I not really getting anywhere with support. They have recognized this as an issue and escalated it to engineering but there hasn't been any update. They aren't offering a work-around so I came up with my own.
1) Sync all your agent settings and agent config to remote core.
2) On remote core, make a copy the Client Connectivity setting and give it an appropriate name (i.e. NOT BORKED)
3) Open up the copy and select your local certificate(s).
4) Make a copy of your agent configuration and name appropriately.
5) Open agent copy and select your new client connectivity setting.
6) Deploy Agents from remote core.
7) Enjoy working agents and wait a really long time for LANDesk to come up with a fix.
8) When fix is released, deploy agent settings update based on the default agent sync'd from your central core.
9) Wipe your brow and say "whew, why couldn't LANDesk have fixed this earlier?"
I'll come back to update this post if support provides an alternate work-around or maybe even a fix.