Perhaps you could test it? It certainly *accepts* multiple URLs in agent mode:
...
ts=2023-06-09T15:22:27.935Z caller=main.go:957 level=info msg="Server is ready to receive web requests."
$ curl -fsS localhost:9091/metrics | grep remote_storage_samples_pending
# HELP prometheus_remote_storage_samples_pending The number of samples pending in the queues shards to be sent to the remote storage.
# TYPE prometheus_remote_storage_samples_pending gauge
prometheus_remote_storage_samples_pending{remote_name="5e94e3",url="http://127.0.0.1:1234/"} 0
prometheus_remote_storage_samples_pending{remote_name="d296a2",url="http://127.0.0.1:1235/"} 0
Whether it actually delivers to both endpoint or not, I have not tested. However, I looked in the source code under tsdb/agent/db.go (the WAL-only database used in agent mode) and I see nothing special that suggests it wouldn't work.
If you find that it doesn't work with multiple remote_write endpoints, then it's a bug one way or the other. At very least, it ought to be changed to reject a config like the one above.