In short, they're using AndroBench's default settings other than changing sequential to 256KB. The default settings are designed to give a huge advantage to UFS in ways that real apps generally do not.
By default, AndroBench uses 8 IO threads for all of its tests. This behavior showed up with AndroBench 4 and continues in AndroBench 4.1.
eMMC is half-duplex, and designed for single-threaded IO tasks. It's not the greatest system, but it is the most common storage in use in Android phones, so applications are going to be designed for eMMC storage instead of the 5 or so phones that are shipping with UFS storage. Multi-threaded IO actually can negatively affect storage performance with eMMC because of resource contention issues, so in general it's rare to see multi-threaded IO in real apps.