Yes.

For instance this monosynth patch that loads two separate waveforms and cross-fades between them:

@mbbaker No, a larger block size will allow the CPU more time to process the audio.

Use a larger block size?

You will have to create the same behavior using what is available indeed. Also checkout compatible abstractions like https://github.com/Wasted-Audio/heavylib (included in plugdata)

In the strictest sense you can use a "list", but not the [list] object.
A list is simply a message that contains multiple values, like [1 2 3 4(

Similarly you can use a table/graphical array (canvas object), but not the [array] object.

vst1 does not exist, do you mean vst2 or vst3?

To host lv2 plugins there is https://github.com/jnonis/pd-lv2
For hosting vst2/3 plugins there is https://github.com/Spacechild1/vstplugin

And no it is not possible to run desktop audio plugins hosted inside a pd patch on the Daisy.
Please see https://wasted-audio.github.io/hvcc/docs/09.supported_vanilla_objects.html for supported objects in the Heavy Compiler.

@timothyschoen relevant ticket: https://github.com/juce-framework/JUCE/issues/333

The issue is no longer specific to Linux, as JUCE now also supports Jack Audio on macOS and Windows (and with the relatively simple patch I published last year it can be easily ported to older versions of JUCE).

Which camera is it? (there seems to be more than one for Raspi)

Make sure you have the v4l2 drivers for it, otherwise it won't be recognized.

Start building custom plugin GUIs using DearImGui:

In what way is this library "designed specifically for Windows 64-bit systems" ?

Also I recommend against committing zip files (and other release binaries) into your repository as it will blow up the repository size when you do updates.
Does Codeberg not support release artifacts?