Since JSON (and custom) fields are capable of storing multiple records, it's safe to use 1 record of 1 table.
As for Seblod favoring just one table, I think superficially that sucks, but on the other hand maybe that's by design.
I see Seblod as 1 article +/- 1 related table front form web "engine", and I build using that as starting point. If there is a need to work with several separate tables all at once, I would use related content and separate input stages (and by that I do not mean form stages).
If, however you would like to do it anyway, there is always JSON and custom storage, which unfortunately do not allow to reuse that content elsewhere.