An example of how to achieve concurrency with Python beyond multiprocessing. The description mentions that nowadays in Python this is used besides multiprocessing that communicate with queues.

This tangential issue in StackOverflow shows actually how to define an own ONNX Session outside Piper TTS, and then pass it to the PiperVoice instance. This could solve the issue with multiprocessing (can't pickle the ONNX session)
Also, explains that ONNX already manages its own threads already. Maybe it's not worth to make it work in a separate Process.

Basically what I'm trying to do but full offline and already polished.
Only in English, they encourage tinkering

Voice, translation and conversational interfaces with a Python SDK that also offers ONNX models, and that looks promising

The example solution in this StackOverflow answer appears to me clear and easy to understand. For my Piper TTS case, try to initialise the worker and have the run loop accepting something to say. Do the same with the eInk and add them all into a Manager. Put in the queue text to say/display, but not a function to execute.

A fast and local neural text-to-speech engine that embeds espeak-ng for phonemization.
Development has moved here. Check if this is what I'm using.

Just in case of running into something like this while tinkering with TTS

Exhaustive official hardware description of all Raspberry Pi versions

In this article, I will try to discuss some misconceptions about Multithreading and explain why they are false.
All experiments are conducted on a machine with 4 cores

In the realm of speech-to-text (STT) technology, achieving high accuracy and efficiency on low-power devices like the Raspberry Pi Zero 2W presents a unique challenge. This report delves into the performance of the VOST STT system when processing simple English language dialogs on such a device. We will explore the issues encountered, particularly the problem of repeated text at the end of buffers, and propose solutions to enhance the system’s performance.