EXCELIMPORT Many Test Cases with Result in a single sheet

You can refer to sample Scripts that create testcases with TCER.cfg/Scripts that create testcases with TCER.xls
to achieve your use case.
In this sample, it will create 6 testcase with scripts associated with it and TCER and results for each test case.
You can comment out testscript related in the cfg file and test it(you may need to change some self-reference to script lines. The working cfg could be like(tested with v5.0.2):

// This configuration file creates a test case with each test script and links them.
// The linking is accomplished by self referential data

// Start looking for scripts after row 2
//testscript.XLSStartRow=2

// use the data in the first row of a found script's column B
//testscript.XLSArtifactID=B
//testscript.dc:title=B
//testscript.dc:description=C

// the literal "execution" will be put into the step type tag, so all steps will be of type execution
//testscript.steps.type=H
//testscript.steps.description=E
//testscript.steps.title=D
//testscript.steps.name=D
//testscript.steps.expectedResult=F
//testscript.steps.property name="comment"=J

// a new script starts when we encounter an empty row
//testscript.XLSDelimeter=\n
testcase.XLSDelimeter=\n   
// we want to use the data we got for each test script to create a test case
//testcase.ID=testscript.XLSArtifactID
// by referring to the testscript's field instead of the column that data comes from
// the tool will also create links to each of the test scripts.
testcase.dc:title=B
testcase.dc:description=C
testcase.XLSArtifactID=B
testcase.priority=G
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCaseDesign","RQM-KEY-TC-DESIGN-TITLE")=C

//execution workitem
executionworkitem.XLSStartRow=2
executionworkitem.XLSDelimeter=\n
executionworkitem.XLSArtifactID="executionworkitem_" & B
executionworkitem.dc:title=B
executionworkitem.testcase=Link(B)

//execution result
executionresult.XLSStartRow=2
executionresult.XLSDelimeter=\n
executionresult.dc:title=executionworkitem.dc:title
executionresult.dc:description=E
executionresult.jzalm:state=J
executionresult.er:starttime=K
executionresult.er:endtime=L
//executionresult.er:stepResults.steptitle=D
//executionresult.er:stepResults.stepname=D
// executionresult.er:stepResults.vg:id=F
//executionresult.er:stepResults.er:steptype=H
//executionresult.er:stepResults.er:result=I
//executionresult.er:stepResults.er:description=E
//executionresult.er:stepResults.er:expectedResult=F
//executionresult.er:stepResults.er:actualResult=F
executionresult.testcase=Link(D)
//executionresult.testscript=Link(B)

If the sample works, you can then fit your testcase, description and results into the xls file and update the cfg file to make your own script work.
Hopefully this helps you to start with.

 In the sample templates that you get with the importer tools look for the template that has multiple TCs or TSs with a row separating each artifact. You can borrow the code from the respective .cfg file to implement similar multi record import into your template.