I'm late to the party here, so apologies.
You could certainly spend a hundred bucks on an I2C interface to interact with the DS2484 and follow the data sheet to do so, but it would be a strange thing to do. This would entail essentially writing a driver for the command set of this device, which I can assure you from working with the command set, you do not want to do. Even if you are capable of this, which is not a sleight (it is non-trivial), you then need to write a driver for each command set of each device that you want to put onto that bus. I can assure you that you do not want to do this.
On top of this, the funny part about this is that the reason one would use a DS248X device is that they are vanishingly cheap and a way to integrate a one-wire bus or buses into a BOM and IC for next to nothing that is surface-mount compatible and very small. Buying an I2C bus and all the overhead and complication to interface with this devices strikes me as funny.
The only reason to do this that I can see would be to test the 1Wire hardware of a deployment system that uses the DS248X for the above reasons I have mentioned, since test hardware like the I2C is expected to cost money and this incremental cost makes sense. Otherwise, you'd be better off just buying a USB adapter like the DS9490 and Maxim's device drivers, or the 1Wire Utilities I've written for this purpose, and lose the DS2484. Save your time for coding you care about, rather than drivers. Glue code doesn't typically gain accolades; the devices you are testing do, however. Spend your time on the latter.
