Using Fluid StandaloneView (also FluidMail) in CLI context - typo3

Question

The name and description of StandaloneView ("Should be used as view if you want to use Fluid without Extbase extensions") suggests, that it is possible to use this view anywhere outside of any Extbase context. E.g. for CLI tasks such as generating emails (FluidMail) or using the view to generate HTML code which is than transformed into a PDF.
Unfortunately none of the above works if the template references assets such as images or CSS/JS files.
The reason is, that the view relys on a request-object to derive the domain-relative paths to the assets, which is obviously not working in CLI as no proper request-object exists:
TYPO3\CMS\Extbase\Mvc\Web\Request prototype object
format => protected "html" (4 chars)
pluginName => protected "" (0 chars)
controllerExtensionName => protected NULL
controllerSubpackageKey => protected NULL
controllerObjectName => protected "" (0 chars)
controllerName => protected "Standard" (8 chars)
controllerActionName => protected "index" (5 chars)
arguments => protected array(empty)
internalArguments => protected array(empty)
dispatched => protected FALSE
originalRequest => protected NULL
originalRequestMappingResults => protected NULL
method => protected "GET" (3 chars)
requestUri => protected "http:///var/www/html/vendor/bin/typo3cms" (40 chars)
baseUri => protected "http:///va/typo3/" (17 chars)
isCached => protected FALSE
The view-helper will create wrong URIs like this:
// f:uri.resource(path:'Css/pdf.css', extensionName: 'myext')
<link href="typo3conf/ext/myext/Resources/Public/Css/pdf.css" rel="stylesheet" />
// f:image(src:'EXT:myext/Resources/Public/Images/logo.png')
<img src="/va/typo3conf/ext/myext/Resources/Public/Images/logo.png" />
The solution given in here does not help, as the template file is rendered/found, but the linked assets are missing which messes up the template completely.
What is a possible solution for this issue? Or: how to work with the StandaloneView in a proper way? Since even the core FluidMail has this issue, it seems to be a general conceptional problem.
Appreciate any input, idea or solution!
PS:
To embed any recourses into the template is no solution!

Answer 1

For people having the same issue und looking for a solution I'll sum up what I already had in mind and what was confirmend by Julian (thanks). If anyone comes up with a better solution, feel free and apprechiated to share.
Solution 1: avoid linking of assets in templates which should be used in CLI contexts and embed all the needed resources inside the template.
Solution 2: faking a ServerRequest with a domain, to allow the ViewHelpers to determine the correct paths for liked assets.
Solution 3: using the BaseUrl helper function of base-url extension
Solution 4: write custom ViewHelpers (or better extending the common ones) which determine the paths to assets not only from the request object, but from the TYPO3 instance path if running as CLI, which should be enough for internal processing.
Still, the name StandaloneView is pretty missleading IMO concidering all the unexpected trouble using it e.g. in CLI context.