If your sensors are not connected to the same computer, then I would recommend against using ROS. What you would need first and foremost would be a reliable and perhaps light-weight way to synchronize streams of data. If bandwidth is an issue then you might care about selectively syncing that data only in support of specific queries – things you want to do with (a subset of) the data. I don’t think ROS is the right tool for that. I would rather look in the IoT space, see what MQTT can do here or maybe RabbitMQ. But I think the real question is: what’s the application? What kind of interesting stuff do you want to do? I think that will drive the decision even more so than the type of data you will be handling.
Perhaps one interesting application I could think of for ROS in this space would be sensor fusion for object tracking. Here ROS’s TF would come in handy to merge the views of the various sensors. But the communication infrastructure would probably still need more than the native ROS pub/sub, which is really meant for “infinite” bandwidth networks, like the loopback device on the robot, where it doesn’t matter much if the same data is sent repeatedly at 100Hz or so.