I see you have an open case with support on this question and we are investigating. I wanted to add a note to this thread just so others that run across this would know. I'll update this thread again when that case is resolved.
FYI for folks that come across this in the future, it is a bug that is confirmed fixed in 2017.3.x. As of this writing that version is not yet available for premise customer but once it is upgrading to it will resolve this issue.