The SNES, unlike e.g. the Genesis, had a really heavy history of using add-on chips on carts. In fact, its entire architecture was very specifically designed to permit and encourage this, which is why e.g. the Genesis 32X had to intercept the video out port on the Genesis, but Super Nintendo carts could just bolt-on a SuperFX/Cx3/SA-1/what-have-you and go about their merry way. (Even the the unreleased Nintendo PlayStation would have been able to directly interface with the existing hardware, not do the 32X route of video interception.)

Where you may be making a valid point is that I don't know how many people outside the dev scene know how common cart-based extra CPUs were. But doing this feels entirely in the spirit of how development on the SNES actually worked, even at the time--and as someone who's done some SNES development work, I knew from the headline alone roughly how it would necessarily be implemented. The closest analog I can think of would be like seeing a blog post, "calling native Win32 from pure JavaScript," and then being disappointed that ffi was involved. That's literally the only way it could possibly work in the first place, so of course that's what it is going to have to be about.