EDIT: Duplicates in sendable DE for MobileConnect is not a duplicate of my question. I recognize that this is a limitation of SFMC and am inquiring about any known workarounds. The linked question does not inquire about any workarounds, in fact, it's basically just asking "why is this happening". I know why it's happening.
Is there any way around this SFMC limitation? I have a sendable data extension I'm using for SMS sending via Automation Studio. The use cases involve potentially having the same mobile number in the data extension multiple times, with the expectation that that mobile number will receive XXX number of messages where they exist XXX times in the data extension. See below - notice my cell number is in here twice, but with different subscriber keys. When I invoke the automation to send this, I only receive a single SMS representing the TOP record, not both, as expected. I figure this is standard out of the box functionality similar to "de-duplicating email subscribers". Is there any way around this limitation, perhaps via a back end business rule setting?