This is an interesting idea. Mark and I wonder if we can just add another version part instead of multiplying the last part of the Firefox version by 100, e.g., Tor Browser based on Firefox 90.0 would use 90.0.0, the first TB patch would use 90.0.1, etc. Another example: Tor Browser with a third patch and based on Firefox 91.0b1 would use 91.0b1.3. We are not sure which scheme is the best choice, but it looks like Mozilla's version comparison code can handle any number of version parts.
This scheme, with the change suggested by brade (using an additional version part for the ${TB_PATCH}) sounds good to me for the releases. For the nightly builds however, I think this will make things more complicate for the script signing updates (#25102 (moved)) which currently assumes that version numbers are based on the date.