With my project maintainer hat on, I don't think putting it into sqlite is the correct approach.
For one, it means extra work by the sqlite developers, to track the ever-changing Unicode spec, or your releases.
For another, the MIT license of the generated code is incompatible with the public domain dedication of sqlite.
For a third, sqlite is often part of a larger system, which will likely have its own way of doing Unicode. If there's a mismatch between the supported Unicode versions then there may be subtle errors not easily caught in testing. While if only ASCII is supported, leaving it up to the application programmer to implement the correct collation method, then that's easy to detect and resolve.
These are just the thoughts I have. I have no affiliation with the sqlite project.
For one, it means extra work by the sqlite developers, to track the ever-changing Unicode spec, or your releases.
For another, the MIT license of the generated code is incompatible with the public domain dedication of sqlite.
For a third, sqlite is often part of a larger system, which will likely have its own way of doing Unicode. If there's a mismatch between the supported Unicode versions then there may be subtle errors not easily caught in testing. While if only ASCII is supported, leaving it up to the application programmer to implement the correct collation method, then that's easy to detect and resolve.
These are just the thoughts I have. I have no affiliation with the sqlite project.