Not a solution to your specific issue (I'm managing my 2012 R2 HV from srv 2016 w/o any problem), but still a solution. With it you can manage practically any HV from any server version.
Amazing that it works for you. I have same error on clean W2016 install, on W10 LTSB 2016 - connecting to any of my Hyper-V 2012 R2 hosts (yet connection from W8.x/Server 2012 R2 clients is perfectly fine)