Refresh and stale elements: findTestObject() returns a TestObject (the locator definition), not a live element. The element is looked up each time a keyword runs, so a page refresh doesn’t invalidate it. Staleness only matters if you store a WebElement (e.g. from WebUI.findWebElement) across a refresh.
Keyword instances: as far as I know, calling a non-static keyword through CustomKeywords.'pkg.Class.method'() creates a new instance of the class on each call, so don’t keep state in instance fields. Use static fields if you need shared state. You can confirm by printing in the constructor.
For repeated elements (menu items, table rows, tabs), best is to go for the test data and use one parameterized Test Object with a variable in the XPath, e.g. //a[text()='${name}'], and pass the value from your page class: findTestObject('Page_X/menu_item', [('name'): 'Reports']).
Common POM guidance is to keep assertions in the test cases and keep page classes for actions, so the same page class works for both passing and failing scenarios.