Feature request: a special kind of s/r~ that ALWAYS has one vector of latency.

from the reference:

"This delay is dependent on a large number of factors including, but not limited to, how many send~ and receive~ objects are involved, if a feedback loop is detected, and the use of different top-level patchers with multiprocessing enabled."

I feel like "but not limited to" is doing a lot of heavy lifting here.
I've found two new circumstances where it ads a vector just this week. And I always have to do at least some experimentation on my own for every use case to make sure it behaves predictably.

If there was an alternative to s/r~ that is locked to one vector of latency a lot of the complexities that come with larger systems would be cut.