Again, nothing in this post will solve your issue, but since the last "unit" on the bus/chain is designated by its ID number and the controller wants to know the last device and last unit number, I have always felt that it should be a drive where this is recorded in its RDB; so I use a HDD there and a CD earlier.
Not sure what you mean here,but setting last unit i.e. in hdtoolbox is just to keep it from wasting time scanning past that ID - you can also set last LUN iirc. that value is written to the RDB.
Since scanning starts at ID 0 it makes sense to have the boot drive low as possible for quicker booting.
A narrow scsi controller actually does not care what the last number is and doesn't need to know.. if no last id is set,on narrow scsi it will scan 0-6 (controller usually 7) and on UWscsi supports 15 devices.
Now in scsi,termination wise the last drive doesn't care what number it is,its just the last drive physically on the last connector.(i know this has nothing to do with what you said above,just a FYI here).
Putting a cd early also slows things since cd's come on the bus slower than the average HD(not always-but in many cases..) In the reality of things this may not make enough difference to change it.
Some like to put the hd at ID 0 and the cdrom at ID5,i never really understood this,makes more sense to me to do ID0 for the hd and say ID1 for the cdrom if its the only other device.
Setting LASTID sometimes can be a pain,if you add a device past the last ID,and forget to edit the rbd to scan to the lastID,then you set there wondering why it doesnt see the drive you added.. lol.
Mech