First from the readMe this has been stated: 
From the above we can see that protocol intends to integrate with any type of erc20 out there, going to this section of the docs too, we can see how this list is quite long.
Now take a look at the implementation of TokenManagerType:
This is used to specify the different possible integrations we can have token wise and is then used during transfers or minting to know the specific nature of the token in order to correctly integrate it.
However, the problem is the fact that when converting in abi.rs for ABI decoding, the below is being implemented:
This current implementation, however, would mean that a tokenManagerType of > 255 would never be supported considering trying to convert it into a uint8 overflows in the @audit tagged instance, which essentially limits the protocol to a maximum of 255 different token manager types.
Borderline low/medium, this is going to completely affect the functionality of types above 255. However, the likelihood of this is quite low, but per the docs in this report and from the protocol they plan to integrate a long list of tokens with different features which increases the likelihood of having a lot of token manager types.
Apply these changes:
Alternatively, if its certain that the protocol will never need more than 255 token manager types, explicitly document this limitation in the code and consider adding a runtime check to ensure the tokenManagerType value never exceeds 255:
