Curtin U's published map defines a long, thin zone stretching from roughly [18.5s, 92e] NW to the coast of Yemen/Oman. This means the sound had to travel between 1,700 and 5,300 miles before reaching the Rottnest detection station.
Speed of sound underwater varies, but if you accept 3,510mph as reasonable, then 1:30am detection time = between 11:59pm (at NW end) and 1:01am (at SE end) event time. Not sure whether the thickness of the region means anything, but it reaches its "fattest" at about 3,150 miles from the sound recorder, which indicates a 12:36am event.
Also relevant: all times above are UTC. Most MH370-related times (e.g. 0:41 take-off, 8:19 postulated time of crash) have been given in Malaysian time = UTC+8h. This means that the event Curtin U has detected took place between 7:59 and 9:01 MYT, or between 7.3 and 8.3 hours into the flight. At the thickest (most likely?) point in the region, the event would have occurred at 8:36 MYT, or 7.9 hours flight time.
If we trust the precision of the 7.5h endurance estimate, the solved-for crash time is 8:11 MYT, which (if the Curtis U event was the crash) gives a solved-for location of around [10N, 60.5E] - the middle of the Arabian Sea.
(The Maldives eyewitness accounts were 6:15 local, or 9:15 MYT, so no corroboration, there.)
All of this requires the Inmarsat data to have been way off - unless something is revealed about THAT, I doubt this new lead will bear fruit.