Good day,is there any legitimate reason behind an item prototype not being able to return the value of LLD macro immediatelly?
For example, if we use vfs.fs.get key for LLD (Zabbix agent passive/active), we already get access to filesystem name as well as the free, total and used space along with the percentage based variants.

{{It would be convenient to map LLD macro *

{#FSPUSED}* to $.bytes.pused.first() and create and item prototype that immediatelly returns the value of *{#FSPUSED}

* instead of having to work around this by creating some dependent item or a script item returning the same value, where the script item has the disadvantage of having to set an update interval and dependent item having to depend on some item outside of the LLD giving extra overhead to this straightforward task.}}