Indexing translated attributes in the core Translatable trait

We are moving plugins from RainLab.Translate to the core Translatable trait. The per-row storage in system_translate_attributes is a clear improvement over the JSON blob, and whereTranslation, transWhere and transOrderBy cover the queries we had before.

The part we are unsure about is lookup by value. With the plugin, ['slug', 'index' => true] copied that attribute into rainlab_translate_indexes, so a slug lookup or a title filter did not have to read the JSON document. The core table indexes (model_type, model_id, locale) and (model_type, model_id, locale, attribute). Those are ideal for loading the translations of a known record. value is a mediumText and is not indexed, and there is no replacement for choosing which attributes should be searchable.

For a non-default locale, transWhere('slug', $slug, $locale) and transWhere('name', '%term%', $locale, 'like') become a condition on the base column or a correlated EXISTS against system_translate_attributes. transOrderBy('name') joins that mediumText and sorts with COALESCE. We have not tested this on a large catalog yet. From the query shape, we are concerned it will become a problem once a table reaches a few thousand rows: every non-default-locale filter or sort has to read or sort value for the whole model, and a LIKE '%term%' cannot use an index on that column.

The migration guide says the index option is unnecessary because every attribute is now queryable. Queryable is enough for reading a record we already have. It is a different cost for finding or ordering records by a translated slug or title.

Is there a plan to support that case on the core table? For example an optional index on chosen attributes, a narrower searchable column beside value, or another approach you want plugin authors to use? If this is intentionally left to the application, what pattern do you recommend for a catalog that filters and sorts by translated name?