My example was "twice by one developer", not "twice across all indexed repos."

A spot check shows that quite a few in your link are used specifically to ensure correct handling of Rust multi-level breaks work syntax, like https://github.com/rust-lang/rust-analyzer/blob/master/crate... , https://github.com/rust-lang/rustfmt/blob/master/tests/sourc... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... and likely more.

Another is a translation of BASIC code to Rust, using break as a form of goto. https://github.com/coding-horror/basic-computer-games/blob/e... . The Python version at https://github.com/coding-horror/basic-computer-games/blob/e... doesn't use that approach.

The example at https://github.com/tokio-rs/mio/blob/master/tests/tcp.rs is a nice one

    // Wait for our TCP stream to connect
    'outer: loop {
        poll.poll(&mut events, None).unwrap();
        for event in events.iter() {
            if event.token() == Token(1) && event.is_writable() {
                break 'outer;
            }
        }
    }

though it can be replaced with a helper-function (note: I don't fully know what the code is doing, but the following looks right):

    def find_writable_event(events):
      for event in events:
         if event.token() == Token(1) and event.is_writable():
             return True
     
    while 1:
      poll.poll(events, None)
      if find_writable_event(events):
         break
   

So while there's likely a good real-world example of something which can't easily be re-written in an alternative form for Python, simply pointing to a grep result isn't all that persuasive.