No, it does not.
Yes, this is what dd does. I get similar speeds to you with a 500mbps connection, so I assume it must just be an rclone mount issue.
Other programs that don't need to support rclone use the files on Google drive. Mount works here as it allows files to appear as a folder.
You need to share a log file for your mount with the issue as it's just guessing.
I am not sure I agree with the statement a mount is 'much slower'.
There is some minor overhead for a mount but it generally should be on par with a copy command.
There should be some overhead for the mount, but nothing major.
Lots of time wasted since the debug log wasn't included in the first attempt.
Quickly looking at other issues, [Solved] Very Slow Read Speed on Rclone Mount - #12 may also be related as the host for the docker container is running kernel 5.4... I'll try and see if I can bump the docker version to beta.
That's just a snippet of a lot so as I said in previous post, need to see a full thing.
Sure. I assume with loglevel=DEBUG. Is the beta version okay to be using?
Why would you be using the beta version?
Please use the latest stable.
Sure. I just tried it due to the bug I linked above. The other tests haven't been with the beta version.
Remember, some of us like to live dangerously 
That assumes you have a working baseline...
If you want to test 'speed, you really want to remove cache as well.
Just make a simple command with defaults, debug log and test on that.
The cache is going to mix and match things and not give you a real idea.
Oops! I think I've solved it. I forgot my rclone was running via a VPN in docker. When I was testing with copy it wasn't being run via the VPN. The VPN is supposed to be running on a server with gigabit internet and via wireguard so the overhead is supposedly minimal, but I guess I'm not getting the speeds I'm supposed to. Either way I think this is solved. Not an rclone issue, a user configuration issue 
!
Thanks all who have helped.
An example on Dropbox with that looks like:
felix@gemini:~/test$ rsync -P jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv /data
jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv
402,423,808 26% 67.34MB/s 0:00:15 ^C
My top scrolled off but my mount command is at the bottom as it's just a snippet:
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 407891968 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 408940544 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 409989120 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 411037696 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 412086272 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 413134848 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 414183424 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 415232000 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 416280576 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 417329152 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 418377728 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 419426304 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ChunkedReader.Read at 420474880 length 1048576 chunkOffset 402653184 chunkSize 536870912
2022/01/24 16:56:34 DEBUG : &{jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv (r)}: Flush:
2022/01/24 16:56:34 DEBUG : &{jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv (r)}: >Flush: err=<nil>
2022/01/24 16:56:34 DEBUG : &{jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv (r)}: Release:
2022/01/24 16:56:34 DEBUG : jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv: ReadFileHandle.Release closing
2022/01/24 16:56:34 DEBUG : &{jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv (r)}: >Release: err=<nil>
2022/01/24 16:56:39 DEBUG : : Statfs:
2022/01/24 16:56:39 DEBUG : : >Statfs: stat={Blocks:53207891968 Bfree:2235957156 Bavail:2235957156 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2022/01/24 16:56:54 DEBUG : : Statfs:
2022/01/24 16:56:54 DEBUG : : >Statfs: stat={Blocks:53207891968 Bfree:2235957156 Bavail:2235957156 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
2022/01/24 16:57:09 DEBUG : : Statfs:
2022/01/24 16:57:09 DEBUG : : >Statfs: stat={Blocks:53207891968 Bfree:2235957156 Bavail:2235957156 Files:1000000000 Ffree:1000000000 Bsize:4096 Namelen:255 Frsize:4096}, err=<nil>
^C2022/01/24 16:57:10 INFO : Signal received: interrupt
2022/01/24 16:57:10 INFO : Dropbox root '': Commiting uploads - please wait...
2022/01/24 16:57:10 ERROR : /home/felix/test: Failed to unmount: exit status 1: fusermount: failed to unmount /home/felix/test: Device or resource busy
2022/01/24 16:57:10 INFO : Exiting...
felix@gemini:~$ rclone mount DB: /home/felix/test -vvv
That makes sense.
Generally try to give specifics like that as well as running a VPN and/or a Docker are questions that are vital to helping solve the issue.
Yeah, completely my fault. If I'm honest, I forgot I was running it with wireguard (and assumed if it was I was getting my speeds!).
I'm actually using some of your configs from your github I believe haha.
Glad you got it figured out. @asdffdsa and myself are Windows users, so that probably contributes to the additional slowness. "Much slower" was perhaps a little exaggerated 
I tend to break things down into 'macro' and 'micro'.
A mount should have a micro performance hit and should not be macro with the caveat of cached files being faster.