The value you see from /proc/ is the default value, and it is 7200 seconds. Setting it to a much lower value would not solve whatever issue it is you're having. More than likely, the router (or DHCP server rather) is renewing the IP lease, which is probably resulting in a new IP address or other disruption to any active connections. Or there is some other problem.
@blandcorporation I have no knowledge of the pro 5 and not seen this before. But, one thing you could try if your not on the dev channel is update to that first and see if that helps. Dev will give you the latest updates for your device just incase it has been fixed already.
If you are already or it doesn't we will need help from someone else.
@ubuntoutou that warning message means or that you have installed in your device a non-xenial app (i.e. a vivid one) or that you have installed an app non-published-yet in the OpenStore (the latter is a pretty common scenario when beta-testing apps straight from the developers repos).
There is no system service or smth similar installed in UT that does battery recalibration. So, if it is not inside the vendor tree of the device that some charging daemon takes care of it, we do not have anything like this. If you can find out how Android deals with that, it would be of great help (some init job that needs to run etc.) - However, I highly doubt that emptying the battery twice to 0% will kill it, especially if it is a new one. Also its strange that a new battery would die so fast when the calibration was for the old one, which normally should mean that the displayed level is below the actual one from the new battery. But I am just speculating.