How do actors or a reactor handle the specific issue of "remote calls to software running in different processes, probably on different machines across a network"? The examples you gave assume that everything can be done in the same process, which isn't always possible. (Eg, a network-based service which uses dedicated GPU hardware for performance reasons, which is too expensive to duplicate for each machine.)
The recovery method will be specific to the remote resource. Eg, if it's often congestion related then a retry with an exponential delay might work. A circuit breaker is just one of many possible fault detection and recovery modes. What language has built-in support for all of them?
Also, I've used this idiom in a different context. Some of my code parses a file containing multiple records, one per line. Some of the records are unparseable, for rare but valid reasons I won't get into. The proper action in that case is to report the problem, skip the record, and go on to the next.
But sometimes people use the wrong format entirely. If (say) 95 of the first 100 records are invalid, then it's very likely that the wrong file was passed as input. In that case, the "circuit breaker" should trip, rather than incorrectly trying to parse the rest of the file, which might have occasional "valid" records. My implementation has a low-level reader, plus an intermediate circuit breaker to add the specific failure policy.
Since your suggested solution doesn't seem to match the problem, and because the referenced idiom applies to more than concurrency, I respectfully disagree with your assessment.