If you’re getting it all in one get, that is coming from the heartbeat log. 
(developer access to the log is limited to those using the SDK, but the bridge itself will use the heartbeat log to respond to an “everything” status request rather than polling each individual device.)
Since you’re going through custom code, you are increasing the amount of work that the cloud is doing for you. It’s non-trivial, But if you’re not seeing any issues in your QOS, it’s your choice for now up until the time SmartThings tells you you are using too many cloud resources. You won’t be able to do it the same way once everything is shifted over to the new platform, but that may be a long way away.
Things that might be impacted by that level of polling would be stuff like the Alexa or Google integration, where the voice assistant might start telling you that they couldn’t do something because the response message didn’t get through in a timely manner. That’s not because of traffic on the Wi-Fi network, that’s because the hub is busy processing the polling requests. But again, if things seem to be working fine, that’s not an issue.
( also, no one but me cares about the following, but there is no “hue hub”. So I assume you meant the bridge.
The Technical Reason why that Hue device is a Bridge, not a Hub )