Not a direct answer to your question but hopefully some helpful information:
If you have the knowledge to write firmware, perhaps you also have the knowledge to write a piece of software that logs all communication between the drive and the reading software. With that data maybe you could see what commands are failing on the drives that will not read the discs. Maybe there are other parameters available in the command descriptor block that will allow the drive to read the disc. Refer to the MMC spec for commands and parameters.
Years ago I helped write a DLL that logs all commands to and all data returned from a drive. The limitation was that the software being used to talk to the drive had to use ASPI otherwise my DLL would not work. My DLL would only intercept data that was intended for 'winaspi32.dll'. It would capture the data, log it to a text file and then pass the same data on to the real 'winaspi32.dll'.
I have no idea what software is being used to read PS3 discs in the Lite On drive. If it uses ASPI, then maybe you could try something similar. If you can find the problem then write your own disc reading software for this purpose.
As Chef seems to be trying to explain, there are many types of UDF, just as there are many types of apples. As I tried to explain, the PS3 disc might very well contain UDF that can be read by most any drive with the correct OS or software. However, that does not mean that every part of the data on the disc is UDF. This would be true for Xbox games. Place an Xbox disc in a PC and you will not see the acutal game files in your operating system. However, the Xbox disc does contain a few files in the UDF 1.02 format that can be viewed but these are just the files that MS wants you to see. The drive can read (most of) the other sectors but the operating system does not recognize them.
As a side note, optical disc drives are not file system aware. They are not programmed to parse the file system (this is the job of the OS). Try burning a small BD ISO file (UDF version 2.50) to a CD and then view the CD in XP. The XP OS will say that there is no disc inserted. This is because XP does not know anything about UDF 2.50. The sectors on the CD will be proper as far as the CD-ROM spec goes but the data will not be understood by XP. Another test would be to install a BD drive in a PC that is running XP and then insert a BD movie disc, such as rented from the movie store. The standard XP operating system will not recognize the disc because it does not understand UDF 2.5. The same drive in Windows 7 will show the files and folders. Optical drives are programmed to read sectors (not file systems) that conform to the specifications that they are designed to read. A CD drive will read data from a CD as long as the CD does not violate the CD specs. Place a DVD or BD disc in a CD only drive and it will not be able to read it. The same is true for DVD and BD. They are designed to read sectors that conform to certain specs. It does not matter to the optical drive what the actual data or file system is.
PS - You will probably get more answers if you refrain from being rude.
PSS - The ECMA-119 spec you linked to earlier clearly states on the first page that it is for CD-ROM (which does not include CD-Audio).