Those IPs are not owned by ZeroTier and do not have anything to do with ZeroTier. I can’t tell you what they are, but I can tell you that they’re not talking to your machine via ZeroTier unless you’ve set up machines in the AWS us-west-1 region & authorized them on your ZeroTier network. And even if you did, they’d show up in your torrent client as the ZT address, not a publicly accessible IP address.
Only thing I can think of is that it’s your torrent client speaking to machines on those public IP addresses for some reason. It’s not ZeroTier though.
; <<>> DiG 9.10.6 <<>> -x 52.53.229.168
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13810
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;168.229.53.52.in-addr.arpa. IN PTR
;; ANSWER SECTION:
168.229.53.52.in-addr.arpa. 300 IN PTR ec2-52-53-229-168.us-west-1.compute.amazonaws.com.
;; Query time: 44 msec
;; SERVER: 10.0.0.3#53(10.0.0.3)
;; WHEN: Tue Jan 26 14:53:10 PST 2021
;; MSG SIZE rcvd: 144
; <<>> DiG 9.10.6 <<>> -x 54.215.207.56
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9666
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;56.207.215.54.in-addr.arpa. IN PTR
;; ANSWER SECTION:
56.207.215.54.in-addr.arpa. 9 IN PTR ec2-54-215-207-56.us-west-1.compute.amazonaws.com.
;; Query time: 44 msec
;; SERVER: 10.0.0.3#53(10.0.0.3)
;; WHEN: Tue Jan 26 14:53:25 PST 2021
;; MSG SIZE rcvd: 144