I said that the alternate-version gTLDs should be reserved for use as proxies. Nobody would be able to register them. Mirroring their canonical TLD would be the

I said that the alternate-version gTLDs should be reserved for use as proxies. Nobody would be able to register them. Mirroring their canonical TLD would be the only thing they do. There would be no gojek.java that would be possible to register; no registrar for .java; no nameservers that hold zone files with .java in their names. There would only be the registrars and nameservers for the canonical TLD .jawa; where these (and other) nameservers would know a TLD canonicalization map [which would be something like the Public Suffix List] that rewrites all .java requests they receive to .jawa requests before the rest of DNS resolution logic takes place. You'd register gojek.jawa, point its NS records at e.g. Cloudflare, and set up a Cloudflare zone for gojek.jawa containing an A record for gojek.jawa pointing to some IP. The registrar would publish a zone file to the .jawa nameserver saying that gojek.jawa has NS records pointing to Cloudflare. You'd be able to see these NS records by asking the .jawa TLD nameserver for NS for gojek.jawa or gojek.java. (Why would you be asking the .jawa nameserver for .java records? Because the root nameservers would point to the .jawa nameserver for both "java." and "jawa.") Cloudflare would publish a zone file to its own nameservers saying that gojek.jawa has A record with value W.X.Y.Z. You'd see this response whether querying Cloudflare's nameserver about gojek.jawa or gojek.java. (Because it also understands the TLD canonicalization mapping.) There would be, in effect, no "materialized" or "reified" .java TLD. It would only exist as 1. an entry in the canonicalization mapping, and 2. an NS record in the root zone.