I just succeeded in exporting code from fuze to my pc ...
Here's how i did it...
Basically the only thing you have is screenshots, so you have to encode text to pixel data.
You can start by wrapping your code in a double quotes. But i'm guessing if your code contains a lot of strings you need to escape them somehow first.
What i did then was make each bit of a character a single pixel. 0 for black and 1 for white. Since i'm using an hdmi capture card to view my switch on the pc i can save screenshots using the windows camera app in 1920x1080 instead of 1280x720 when using switches screenshot features. so in a single full hd screenshot i can store 1920x1080 / 8 characters which if using 100 characters per line (which is never the case) would result in saving about 2600 lines of code in a single screenshot.
Since both switch as my camera app save pictures in jpeg, which is a lossy format you have to counteract jpeg artifacts. Basically what i do on the pc is created a program that checks every pixel's RGB value and if R < 128 and G < 128 and B < 128 i consider it 0 bit otherwise a 1 bit and then you just reconstruct the text. and i stop processing the picture if i encounter the 0 character. One other thing you have todo if using windows is when you encounter the 10 char (linefeed) is to replace it with 13 10 or your return characters won't display correctly
This a screenshot of how such encoded screenshot looks like for the program in the 1st screenshot (1st 3 rows of pixel data)
if you save the image and zoom in you'll see what i mean lossy jpeg format (jpeg artifacts).
So now you can code a fuze code exporter yourself :)
I'm not sure if checking for half the pixel value for black / white is enough to counter act the jpeg artifacts all the time but it did seem to work with my test code / screenshot
also when using switches screenshot system you probably have to enforce 1280x720 even in docked mode or you might loose pixel data if they do not save the screenshots as full hd