LOL!!
After this morning's update to the CA2A as offered by Cakewalk CC, I now see the CA2A as a Prochannel plugin.
THANK YOU! Cakewalk, 
as a sidenote, if this was indeed corrected as a result of this thread then hats off to those who corrected the issue so quickly.//although they may have been aware of it beforehand.
CClarry, please confirm if corrected for you as well. 

From what I see, build 112 was moved from Early Release to Production yesterday. This build of CA-2A was released to the public on Dec 22 2016. Had you installed this build in December, the only thing you would have noticed yesterday was the install indicator changed from yellow to green.

Hello, Actually, I am now able to see and use the CA2A as both a plugin and a PROCHANNEL one. Prior to that the Prochannel ca2a was not available.

As I mentioned before there are only 2 binaries for the CA-2A, one is VST3 format and the other is VST2 format. Any plug-in determined to be a PC module by the Vstscan.exe has its registry inventory record isInternal entry set to 1. A VST2 can load in the FX bin or as a PC module if it is coded to do so. The CA-2A may not have appeared as a PC module because the VST2 dll did not scan correctly or the dll was not in the scan path. The plug-in would still show up in the FX rack and browser menus because the VST3 was installed and scanned. The CA-2A has always relied on the VST2 dll to load as the full VST2 in the FX rack and as a PC module. Now that the VST2 has scanned correctly without restoring the machine to a configuration where the plug-in did not appear as a PC module, it would be hard to tell why it failed in the past.

Hello Scook, thank you very much for that most informative read, I will check to see if any of those criteria were at play, thanks again.
At this point, I am glad to have both versions fully functional.
Thanks again.

lgmab
At this point, I am glad to have both versions fully functional.

This is the important part. I was just trying to explain a little about how the plug-in works.

Absolutely, this info will also help for future trouble shooting, thanks again!

After installing the new update it's back...

Yup, it must have been corrected somehow, Check out Scook's comments above, good stuff to know.