Hello Isman, thanks for your reply.
I thought nothing inside the generated config.json would contain the actual hostname aside from the the hostname key and upon starting oxauth/oxtrust they would generate those hostname-tied configs accordingly. But I understand now it's done by the config-init generate so it makes sense in a way.
I ended up just changing the base64 value and updating it with different hostnames depending on where we run the deploy.
Reason I'm doing this is because we're re-using the same generated config for multiple deployments but on different hosts by updating some values and keys/certs inside config.json applicable for that host. But it's working so all is good ;)