Thanks for your answer.
I already extended/customized/patched the hibernate-tools which I use it for reverse engineering.
The biggest issue is related to the fact that there are no foreign keys defined between tables that have relations defined.
Even if I want to define/add the Foreign-Key at the database level by including the First Spirit field (<shortened table name>_FS_ID), this wouldn't work because in the primary key are used timestamps. Just imagine there is a PARENT(1) - (*)CHILDREN relation between the two tables, where the parent record has 3 children related records. Because of the timestamps (which are different for each record from the two tables) the foreign key will not work.
Also, there can not be added a foreign key based on the <shortened tablename>_FS_ID field because there is no matching unique or primary key for it (since the <shortened table name>_FS_ID could appear many times depending of the versioning).
On top of these issues, the filtering must support "release filtering" and "current state filtering".
...based on this your suggestion with DelegatingReverseEngineeringStrategy doesn't fit. Thanks anyway.
So, basically from this point of view the hibernate tool does not support First Spirit standards/style (there are many aspects).
In the end I had to do more customization to the hibernate-tool, including changed and new templates in order to support FS at DB level - for reverse engineering.