Why not shift over indexing by one consistently? So you'd use {3, 4} and {3, 3} for each, so the length property is preserved.
("12345"):sub(3,3) returns "3", while ("12345"):sub(3,4) returns "34", and ("12345"):sub(3,2) returns "".
Indexing in the array portion of tables, and strings, is at least consistent; but Djikstra was right.
The Wiki[0] has a good discussion of Djikstra's iconic essay. The best of these arguments, imho: 0 based indexing unifies enumeration and measurement.
FWIW, I think that the real mistake was to make inclusivity/exclusivity implicit to begin with. If the syntax is explicit, and the choice is captured in the resulting value (i.e. it's more than just a pair of numbers), then you just use whatever is more convenient for the task at hand. Nim almost gets there: (x .. y) is end-inclusive, and (x ..< y) is end-exclusive - but the syntax still exhibits a preference.
Swift is similar, using `...` and `..<`. Rust uses an alternative convention, `..=` and `..`.
Would you prefer to see `..=` and `..<` so that inclusivity/exclusivity is always explicit?
To mark a node at the third position, containing one character, we say {3,3}.
But what if there's a node at the third position, that contains no character? Well, thats {3,2}.
It's like nails on a chalkboard every time. 1-based indexing is a mistake.
~=, by contrast, is just notation. You get used to it quickly.