The problem with this is that you are trying to combine two different tunnel modes: "Indexing" for the array and "Last value" for the boolean. This will most likely lead to more confusion than the way it's currently implemented.
dgdgomez: Your suggestion would provide an output to answer the question "is the output array empty?". Useful, but it succumbs to the same confusing-to-read problem as the original suggestion. Speaking for myself alone, I think there are too many ways to interpret that output value for me to be comfortable with us creating any output value. You propose an "or" output... why not an "and" output? Having said that, your proposal is both less confusing and more useful to me than the original idea posted here.
I'm going to recommend to NI that we Decline this idea, but, dgdgomez, your idea is sufficiently different, you might consider posting it as a new idea and see what kind of traction it gets. Even though it feels problematic to me personally, I can definitely see its utility in code.
Completely independent, border tunnels that accumulate logical values on a loop would be nice -- a lot easier than coding up a shift register would be to just have either an Or or an And on the border of the loop. Similar for Sum and Product for numerics. There's just so little space in the art of a tunnel, we would probably need some new node syntax on the loop boundaries entirely. It's syntactic sugar that has never been a priority for me, but I've certainly kicked the tires on the idea over the years. I think there's some idea exchange posts around that explore similar ideas.
Declined for reasons listed in the idea thread.