You can link Items and Folders to Custom Objects. Unfortunately, the "Where Used" information is not directly accessible. To workaround, you need to evaluate the custom objects' content. I have an implementation sample as part of the extended Data Standard sample: the selected ECO is linked to multiple tasks:

The code to list these "Where Used" links is the variable _allCustents, a search result that returns all tasks. The loop iterates these and checks for active links. This approach is highly risky in impacting performance; the code snippet below is for "demo purposes" only, as the search may return thousands of custom objects. But, if you create links programmatically, the code can add more properties to the link target, optimizing the search. My implementation limits the search result leveraging the names of the tasks including the ECO number.
$_allCustents = mgetCustomEntityList $_CoName
$_LinkedCustentIDs = @()
Foreach ($_Custent in $_allCustents)
{
$_AllLinks1 = $vault.DocumentService.GetLinksByParentIds(@($_Custent.Id),@("CO"))
If($_AllLinks1) #the current custent has links; check that the current ECO is one of these link's target
{
$_match = $_AllLinks1 | Where { $_.ToEntId -eq $mCoId }
If($_match){ $_LinkedCustentIDs += $_Custent.Id}
}
}
Markus Koechl
Solutions Engineer PDM, Autodesk Central Europe