From a comment on the question:
I am going directly off of what's on their website.
mellbell.cc/products/pico What they show on the link you provided is a
prototype.
The "link you provided" refers to this, which despite being described as for a "prototype", shows correct information with regard to the SPI related pins.
As it turns out the documentation in the images you referenced at mellbell.cc/products/pico is incorrect, both under the product shots and in the pin-outs section under "Documentation". You can tell this by looking right at their image of their board and their diagram, and comparing that with the pinout of the ATMega32U4 itself:

Interestingly, in the pinout on 8 of their PDF in the documentation section, they have it correct again and closer to the prototype:

Or at least it is with respect to the SPI signals. The diode is in the wrong and orientation. In fact, the whole board seems to be left-right reversed.
Again, from the same comment:
Additional research also shows that the SCK and MISO pins
I'm connected to seem to be for programming only
It is true that these pins are used for ISP programming. However, they also carry the data for the SPI bus peripheral when you're not doing ISP programming. So they are "for programming" just not "only" for programming. This is down to how the ATMega32U4 is, and not something tha the Pico makers have much control over.
This is also the case for UNO and basically all of the other popular AVR based Arduinos that can be programmed using the ISP method, as opposed to uPDI and others. What slightly less common is to have these pins only available as unpopulated pads or only available on the ISP header.
I can see why you might want to not deal with those contacts because of the form factor of the Pico board. However, because those pins are actually 32u4's SPI interface, and they should perform better than the bit-banging that Adafruit library would need to resort to in order to use other (non-SPI) pins. So there is an incentive to use them.
So, your solution is a solution, but not for the reasons you think. The pins you were previously trying to use will work when your efforts aren't being undermined by bad documentation, and you get them in the right order.