This behavior sounds like it should be how your loop end node should work, not necessarily a node within a loop body, as you won’t really be able to put any node behind this one and have your loop continue to run.
Do you plan to accumulate some state during the loop executions and return the final state in the last iteration? While this might be technically possible by making use of Flowvariables being sent from the Loop Start node downstream, nodes within a loop body should really note carry data state between iterations, you are opening the door to many problems with inconsistent node behavior with this. For example: what happens when I put such a node outside a loop? What if I want to only perform one loop step and view the intermediate results? …
What exists as a concept in KNIME is a Recursive Loop nodes, which allow you to pass data from one iteration to the next:
Also the Active Learn Loop node combines recursive loop results one one port still providing the original input on a different one.
I think doing something in that direction should be a good start.