Thank you to both of you for your valuable insights!
To be honest I am not sure if I get the sni-limitation-feature correctly, maybe you, @unic3rn can point me to additional documentation (I tried to find additional info, but was not successfull).
As far as I understand my part as a bridge-operator would be to make sure, that my webbridge does either acceppt an SNI given (catchall, like you linked with __ in nginx) or I would make my webserver accept an additional SNI (example .com and vk . ru).
On the client side lyrebird would take care about resolving vk .ru to 1.1.1.1 (in your example) and ignoring the failed TLS-check for vk .ru. correct?
Regarding the sni-limitation in torrc, as an operator I don’t actually create the bridge-line. It is generated from contents from the torrc (like sni and path) and the relays fingerprint. As far as I know, I can add anything sni-limitation-specific to the torrc yet.
Additionally: since it’s the SNI that get blocked, wouldn’t it help to have multiple SNI pointed to the same relay? Server capacity (and IPv4 adresses) are expensive, domains aren’t. The problem here seems to be that I can only set one URL in torrc, therefore I would to run multiple tor-processes each with it’s own torrc.