Restoration network speed limited to 100MBits/s

Welcome to the forum @Ripod

Big Comparison - Borg vs Restic vs Arq 5 vs Duplicacy vs Duplicati is one of the better studies.
Posts to the forum don’t go to everyone, so only people who read a lot will notice your latest ask.
One concern I have with the above comparison (and with your test method) is whether they use

no-local-blocks

Duplicati will attempt to use data from source files to minimize the amount of downloaded data. Use this option to skip this optimization and only use remote data.

because without this, as little as possible goes over the network – which is the metric you chose.

For whatever it’s worth, I ran a OneDrive restore with no-local-blocks and got about 60 Mbit/s.
That was seen in Task Manager with Update speed set to low, trying to visually average a graph.

The way one gets fast network performance is often through parallelism, just as with CPU cores.

Increase the number of concurrent requests suggests azcopy on 16 logical processors gets 256.
You can study whatever tools you use, or maybe even view the connection counts using netstat.

  --asynchronous-concurrent-upload-limit (Integer): The number of concurrent
    uploads allowed
    When performing asynchronous uploads, the maximum number of concurrent
    uploads allowed. Set to zero to disable the limit.
    * default value: 4

works for backups. Restores are single-threaded. Watch About → Show log → Live → Information
If you want a pure Azure download test, use your URL in Duplicati.CommandLine.BackendTool.exe

A network-only restore is usually limited by download rate, but also keep no-local-blocks in mind
because (depending on the setup) its shortcut can get a lower download speed than restore speed.