As soon as I backed out that 2nd telemetry entry, HIVE started being able to see the hash rate again. I also tried using a different port for the 2nd telemetry entry, but it still broke HIVE. So it seems to me that when a 2nd telemetry entry is added, it replaces the first one.
one hacky work-around is to edithive/bin/dstm and change the telemetry line:
echo -e "--telemetry=0.0.0.0:43000 --time --temp-target 82" > $MINER_CONFIG
now it listens on all interfaces, and keeps hive os happy and awesome miner can also connect on that port to the internal IP of the rig.