For short-term storage, your pass-if/add nodes can be replaced by buffer nodes.
You will need to figure out which buffer to send the Done pulse to; gate nodes could be used to help with that.
The patch has no output to indicate when it has completed a cycle. Looking at the output before it has completed its 1st cycle will result in 0 values for outputs that have not been calculated yet. There is also no input to indicate when it should start or a way to change the angle of the sensor between each reading.
Why do you calculate the range 5 times and only store the last time?
The ultrasonic range finder needs time to settle down between pings. Once every second might be cutting it close. With this setup, it will take 15 seconds to complete a loop. If your robot is moving, 15 seconds is a long time to be moving between checks to see if you will hit anything. You will either need to be moving very slowly, or use a pretty long distance to indicate robot should stop to avoid hitting anything. I assume your long-term plan is to use OUT1 as distance to object to the left, OUT2 distance in center, and OUT3 distance to the right. If robot is moving during these calculations, at least one of those readings is from at 5-10 seconds ago and could be very different now. With your current code, angle would need to be calculated from count if you want OUT* to represent a specific direction.
Why not write your patch to accept a start pulse, which positions the sensor (you will need a delay here so servo has time to move to new position before sensor sends ping), then tells the built-in ultrasonic sensor node to ping, and feed the output to one of your output pins, then route pulse to position sensor to new position and tell another copy of the sensor node to ping and feed that output to another pin, etc., then send pulse to a done pin for the patch. Each copy of the ultrasonic node will keep its value until it receives another pulse to update. Note that any of the ultrasonic nodes might send an error pulse instead of a done pulse; your code will need to process that so the pulse controlling your program flow doesn’t get lost and leave your program hung.
Do you intend to turn your robot even if you are not about to hit anything? If not, you really don’t care about distance to side until you are about to hit something, at which point you could stop your robot and check distance to each side. This would make your robot much more responsive since you don’t have to wait for servo to re-position and extra pings while you are moving forward (which might result in hitting an object before you see it in front of you).