Short answer - "no".
Longer answer - "it'd be a supreme hack, that I rather doubt would work".
You'd essentially have to hack together bits from a 2017.3 Core into a 2016 system ... it's a recipe for problems / disaster if ever there was one (a fair few code changes are needed to take on BitDefender. We're not talking about just "putting a new GUI on" here ).
So ... long & short of it - "no" (sorry). Not what you were expecting to hear, and I understand where the idea comes from ... but it's a bad idea.
Thanks for the response. That is what I was afraid of.
The end result that I would like is to move away from Kaspersky to BitDefender. We are currently on 2016.3 running Kaspersky as our AV. I was hoping to stay on this version to do the AV transition.
I'm assuming our path for moving to BitDefender would be to move to Ivanti 2017 first. Does the move to Ivanti 2017 break Kaspersky support?
No - it does not.
EPM 2017 (you'd want to grab the 2017.3 version -- probably with SU4 for eval, you may request that from support, when it is out), is effectively supporting 2 AV-s at present (Kaspersky & BitDefender).
That sounds like a plan. Thanks for the info.