Interesting question. I think I understand what you want, present one view of a current record, allow the user to fill it in and submit, then display the next record until all records are complete? (and this could possibly happen out order)
It is possible, using secondary data sources, and lots of web services data connections and rules..... Although I question your platitude that a repeating section 'looks too busy'. A form is how you want to develop and display it hence a repeating section/table isn't necessarily your foe. You could write code to drive the form, you can do whatever you want to accept the input you require.
Is what you want is a form that doesn't save any data, although it accepts data and sends that to the SQL DB and then accepts the next set of data until all have been complete?