This is interesting, but I feel like it only scratches the surface. What about all the types that _aren’t_ an int or a pointer?
If you have a record type, or anything else, that'll compile to a pointer and an object in memory, comparable to e.g. Python or Java objects.
Types like booleans are converted to integers by the compiler, similarly to C(++) (though there's no implicit conversion on the language level).
This is the "float boxing" problem - floats cost an extra pointer chase in most cases. The 63-bit int is an optimization that avoids needing the extra indirection for ints. You can still have 64-bit ints, but they aren't the default, and they cost this extra pointer chase.