Is it smart to use Spring Data in a project?

Question

Java

There is a need to make the backend of the project. Web - part will be installed locally to each client (or on the server to the client). The bottom line is that the project involves dynamic CRUD of tables and columns, so the classic ORM approach can only be used in system tables (which will be unchanged), while CRUD is also needed for tables created by the user. That is, a pool of parameters will come to the server, which will need to be turned into an INSERT (and not only) request.
I have these questions:

1. Does the ORM (and implementations, hibernate in particular) have options for such situations? I mean patterns, some architectural solutions.
   
2. How customizable is spring data(hibernate)?
   
3. In general, is it reasonable to use it?
   
4. What would you do?
   

PS Using java is important. I understand that in a language with dynamic typing, there would be fewer problems, but java.

Answer 1

What would you do?

Choose the right tools for this task. That is, I would get rid of Java, Spring and a relational DBMS.