jool clat for 464xlat script

clat-jool.lte.sh

#!/bin/bash

PREFIX="$1"
IFACE="$2"

ip netns add jool
ip link add name to_jool typ veth peer name to_world
ip link set up dev to_jool
ip link set dev to_world netns jool
ip netns exec jool ip link set up dev to_world

ip -6 address add scope link fe80::1/64 dev to_jool
ip netns exec jool ip -6 address add scope link fe80::2/64 dev to_world

ip netns exec jool ip -6 route add default via fe80::1 dev to_world
ip netns exec jool ip -4 address add 192.0.0.2/29 dev to_world

echo 1 > /proc/sys/net/ipv6/conf/${IFACE}/proxy_ndp 
ip -6 neigh add proxy ${PREFIX}::4646 dev ${IFACE}
ip -6 route add ${PREFIX}::4646 via fe80::2 dev to_jool
ip -4 address add 192.0.0.1/29 dev to_jool
ip -4 route add default via 192.0.0.2 dev to_jool
echo 1 | tee /proc/sys/net/ipv6/conf/*/forwarding

ip netns exec jool modprobe jool_siit

ip netns exec jool jool_siit instance add --netfilter -6  64:ff9b::/96
ip netns exec jool jool_siit eamt add 192.0.0.1 ${PREFIX}::4646

for use in a single /64 e.g. when connected to LTE, don't use it at WIFI, in case a other user uses the same script, the clat ipv6 address isn't randomized here

Could this be done without jool_siit?

I am not sure if the script still works, since jool is still under heavy development.
But to your question, the answer is no.
Something has to do the translation. jool_siit, tayga or tundra-nat64 or an other app or kernel module.