Use case for URL alias

Hello,

I have a use case for each URL alias create a custom replace token, so, if there are a lot of aliases, that will also create a lot of custom tokens, in this way, the single table of database will create a lot of records, if there are more than ten million records, its performance will decline, whether can by custom create tables to store custom token datas in the database.

The default two database tables:
token_custom
token_custom_field_data

If can customize to create tables:
token_customone
token_customone_field_data

token_customtwo
token_customtwo_field_data

...

Customone and customtwo for custom table name by user.

If can do, there are more complex functions:
Custom token replacement value can add fields by custom such as the manage fields of the content types.

E.g. token_customone_field_mytoken

And use custom token like this: [custom:machine_name:field_name:0] (Multi-value field)